I vote for making the load/save behavior configurable. As it stands,
debugging Session-related code is made significantly more inconvenient,
because every time you need to test code you have to stop the appserver,
hunt down the session files it laid, delete them, then restart the
appserver. That can be a PITA.

-----Original Message-----
From: Geoffrey Talvola [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 11, 2001 4:19 PM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: [Webware-discuss] FW: session management


It could be considered either a problem or a feature, depending on your
viewpoint :-)

For efficiency reasons, you might want all session data to be stored in
memory while the appserver is running.  But you still want the ability to
stop and restart the appserver without losing your session data, so it
makes sense to save the sessions to disk on shutdown and load them on
startup.  This is what the Memory store does.

If you like my interpretation, then it follows that it's OneShot that has
the problem -- it should also be loading and saving the sessions.

Or perhaps the load/save behavior should be configurable -- that way you
get to choose whether restarting the appserver preserves sessions or wipes
them out.


--

- Geoff Talvola
   [EMAIL PROTECTED]


_______________________________________________
Webware-discuss mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-discuss

Reply via email to