> That's what i concern now. I am using database, however, I am no idea on the
"clean up" the field values if user logged out in not general procedure....
Can I using session_onend in global.asa?
or write some stored procedure or function inside sql server and run it
scheduly?
Hi there,
In addition to the 'is_loggedin' attribute, you can add a 'last_request' datetime
value. Each time the user sends a request to the server, this field is updated.
Regularly, from example every 20 minutes, simply run a background check to
detect who didn't send any request during the last timeout delay. You'll know
who didn't click the 'Logoff' button and if you've time enough to lose, you can
even send a tip "how to quit" to those users ; )
About the persistence mechanism... I suggested a database but if you could
also store it in a simple Application wide variable, as this information is clearly
designed to be reset after an application start.
Antonio