| Neil,
If you are opening a new session for each browser connection then you can use that session count. Since you'll already have available a time-out for each session & it handles multiple logins from the same ID, but from different browsers (sessions). However, opening a new session is an expensive operation unless you need to maintain state between pages. You can optimize this a bit by killing sessions that you don't really need.
You can put and remove the session IDs into a hash table stored in application scope via HttpSessionActivationListener. When you want to check the session counts you ask for the current size of the hashtable.
Niels On Mar 5, 2006, at 9:52 AM, Neil Alexander wrote: Hi All,
I'd like to have an indicator that shows how many connections are currently looking at a site. Superficially, it looks fairly simple, but then getting into time-outs, different parts of the site, multiple logins with same name (which I actually don't want), etc. It looks a bit tricky.
I would prefer a jsp solution, but a WebService would work, too.
Any code lying around that does this type of thing?
Thanks,
Neil Alexander
|
