Jon Stevens typed the following on 06:35 PM 12/29/2000 -0800
>> I can see this being used for fault tolerance. If your servlet engine
>crashes,
>> or if you have to restart it for some reasons, your users' sessions don't
>need
>> to be lost.
>
>If the server crashes, then you are screwed either way.
If it crashes and is restarted quickly, it can load the serialized sessions
from disk and users can carry on. This assumes you've got some kind
of script watching and restarting the server process.
>If you are live, then serializing/deserializing the sessions for each and
>every request could be a major slowdown (even with this code).
It doesn't need to. I'm writing PersistentManager to put the session
on a queue to be serialized by another thread. This shouldn't have a
noticeable performance impact.
Kief
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
