Re: Track the users on line?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

re:
But doesn't the session close the channel when the user close the browser?

No. It closes the session after the number of minutes specified in web.config
for the sessionstate's timeout value has expired and the user hasn't requested
a page in at least that time.

re:
So.

So, your premise is mistaken, so your method can't work.



Juan T. Llibre, asp.net MVP
aspnetfaq.com : http://www.aspnetfaq.com/
asp.net faq : http://asp.net.do/faq/
foros de asp.net, en español : http://asp.net.do/foros/
===================================
"andrea" <googlegroups@xxxxxxxxxxx> wrote in message
news:9fa0d7351a6218c8181dc08710b0@xxxxxxxxxxxxxxxxxxxxx
But doesn't the session close the channel when the user close the browser?
Isn't the same if user change site? So I suppose that simply entering a valid URI
into the address bar, shouldn't open a new session.

But what I mean is - in this case - a session track for user that has been authenticated.

So.
A valid url, or homepage, add +1 to the global counter ... that's fine ... and impossible
to trap. A user login, update table flag to know that user has logged into the system.
If he try again to log from a new browser, the check for the flag doesn't allow the access.
If a browser will close without pass for the appropriate log off button, the flag remain there
since lastlogin field on the db + 20 minutes doesn't allow the next user who try the login to
update all users flag to not logged.
This is system I've used. And always works. But not solved the spot user that isn't logged in.
For that the best way - I think - is simply doesn't care.

What do you do generally?

Bye
Andrea





.

Quantcast