Chris Backas wrote: > Hi Geoff, > > Things have become slightly more interesting; I did as you > suggest and > I put a timeout extension in awake() and restore it to normal in > sleep(), however, it seems that our REAL problem is the 'soft' timeout > that occurs when an idle session is serialized to disk. I have code > that goes through our DB pool and closes off connections that are > unique to the user when the session is written to disk, and this is > running in the middle of the processing. Is there a similar technique > to temporarily disable/extend the serialization? >
I'm sure there's something you could hack into the session sweeping code. Maybe you could add a flag to the session object that says "do not serialize" and check for that flag in the session sweeping code. I suspect it would be a tiny code change. Sorry I don't have a more specific answer but I don't really want to dig through the code right now. - Geoff ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
