The posts regarding the low number of concurrent users causing issues and the need to scale AwareIM are making me wonder ...
Is AwareIM stateless as is typically the case with web applications?
In a typical web application ... concurrent users means that there is an active connection and/or server process (performing logic, reads/writes to db, etc) running on behalf of each user at a give moment in time.
If the user just has the screen up, but the system is idle, that user should NOT be included in the count of concurrent users.
Meaning 40-50 users logged in at the same time is MUCH different than "concurrent" users when it comes to the load an application can handle.
But maybe AwareIM ....
Is maintaining an active connection to the server?
Is maintaining a large amount of session data in memory on behalf of each user that is logged in?
Thanks,
JT