DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5829>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5829 StandardManager needs to cope with sessions throwing exception in read/write ------- Additional Comments From [EMAIL PROTECTED] 2002-06-21 18:21 ------- Humm... I gave this some more thought. How about an extra layer of abstraction. Namely each session is serialized in memory, then the byte array is written to the object stream. Thus unserializable sessions will not be saved. Also, when restoring sessions if a session cannot be de-serialized (missing clases or whatever), the next session in the stream can still be read and restored. What do you think? -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
