You are correct that you can obviously store data in a server side database,
or a text file even - but it implies that you have information about your
user that identifies them as each new session begins - and in fact a
database to actually hold the values in. Drew could of course also use the
application object byt that itself does not offer persistence between
applications recycling.
If you read the thread - Drew was asking how to persist the username between
sessions in case of timeout. If he is getting the user name at login from a
server side store why would he need to persist it between timeouts at all?
Perhaps I should have said the "easiest way" to persist was with a cookie,
rather than the "only way", as any server side storage between sessions
implies requiring knowledge about the remote user it is by far the most
straightforward approach.
Regards
John Timney
Microsoft Regional Director
Microsoft MVP
"Mark Rae" <ma**@mark-N-O-S-P-A-M-rae.co.uk> wrote in message
news:ub**************@TK2MSFTNGP12.phx.gbl...
"John Timney (Microsoft MVP)" <ti*****@despammed.com> wrote in message
news:OT****************@TK2MSFTNGP10.phx.gbl...
The only way to avoid loss of data on a timeout is to use a cookie and store your values in there, as cookies can persist between sessions.
Rubbish! If you *really* want to persists data between sessions, store it
in a server-side database.