Howdy, >> >> Sessions are not meant to be persisted across server restarts. >> > >Obviously other people have other opinions about that.
Which is why I still suggested a solution I've used in the past ;) Even though I disagree with the approach of persisting someone else's proprietary internal objects, I assume that whoever asked the question has a reasonable and well-thought out cause, so I try to help. I'm still unclear as to why one would want to save the session object itself, as opposed to only the parts of interest from it. Does it have to do with load-balancing, wanting to somehow augment / superimpose on the built-in mechanism? Yoav Shapira Millennium ChemInformatics
This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you.
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
