My workaround in 0.7 is to comment out the code that stores Memory sessions to disk (which in my mind it should anyway). Memory to me implies transient, not persistent. I also believe that storing sessions to disk is a security hole as well in mnay cases but that may just be me. It would be as easy as changing the Session code to having Memory Sessions never persist between application restarts. That way they would just go away after they timed out.
Mike Engelhart
On Tuesday, January 28, 2003, at 09:57 AM, Stuart Donaldson wrote:
Which version of Webware are you using?From the looks of the trace back you provided, it appears the problem isthat the decoding of the serialized session on the disk is failing, rather
than the session is missing.
This can be caused by having non-serializable objects in the Session object.
Until recently, the problem would show up just like this, because the
pickled session object was corrupted since the entire object could not be
stored.
The current behavior (as of 0.8b1) is to display an error when trying to
pickle the session out to disk, and to not store a corrupted session on
disk. The error goes through the Application.handleException() method which
by default will print the message to stdout.
Note you won't see the pickling exception in your browser because there is
no session associated with the error.
If you are using 0.8b1, please let me know, as there must be some other
problem.
But generally I suspect your problem is that you have something in the
session object which can't be pickled like an open file or database
connection.
-Stuart-
------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
