It is not 100% reliable since if ASPNetworkProcess dies and restarts
or because of obscure bug 100% of people may not be logged out.
I would always when they interact with a page update a
"LastInteraction" datetime field in a table. That would have 2
advantages
1.
you could customize and allow some users longer timeouts or shorter ones
2.
You could still use session end in non-customized users to logout some
of the people to supplement whenever you sweep the "LastInteraction"
fields to log people out.
The only question in this scenario is when to sweep "lastInteraction"
but a clever programmer will think of several choices.
On Thu, 20 Jan 2005 18:45:42 -0700, Ali Husain <[EMAIL PROTECTED]> wrote:
> Charles. thanks for the info on session End, I always wondered about
> that as well. Is it poor programming to use session end to determine
> someone who never logged out and then remove them from a list of
> currently logged on users?
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
