Friday, June 18, 2004 4:04 PM
To: [EMAIL PROTECTED]
Subject: Re: Concurrent Users
In continuation to the same problem I have two issues.
1. httpSessionListner Interface sounds good but as per my knowledge
sessionDestroyed() method will not be called if browser
In continuation to the
same problem I have two issues.
1. httpSessionListner Interface sounds good but as per my knowledge
sessionDestroyed() method will not be called if browser is closed, so
it's difficult to manage concurrency.
2. let say my 'user' class implements httpSessionListner. I have
t
> Sent: Wednesday, June 16, 2004 9:23 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Concurrent Users
>
> Two things to note. Since there is no way to positively no when
a user
> has left your site, there's no accurate way of knowing how many users
> are currently viewing y
ology. [mailto:[EMAIL PROTECTED] On Behalf Of
Chris Pratt
Sent: Wednesday, June 16, 2004 9:23 PM
To: [EMAIL PROTECTED]
Subject: Re: Concurrent Users
Two things to note. Since there is no way to positively no when a user
has left your site, there's no accurate way of knowing how many users
are current
Two things to note. Since there is no way to positively no when a user has left your
site, there's no accurate way of knowing how many users are currently viewing your
site. With that said, if you want to count the number of outstanding users whose
sessions have not timed out, make a User obje
You can keep a class level variable. Increment that when the user joins in
the session and decrement that when the session times out or when you
invalidate the session.
From: Khalid Umar <[EMAIL PROTECTED]>
Reply-To: "A mailing list for discussion about Sun Microsystem's Java
Servlet API T
