Chuck Esterbrook wrote:
What if you created a SessionFilePerKeyStore which stored each key in the session dictionary in a separate file? It doesn't eliminate the problem entirely, but it might mitigate it enough. For example, if Page B is mucking with different session data than Page A there won't be any clobbering. I don't know if that applies to your particular app or not.
That will work as long as none of your session variables depend on each other. Why not lock the session with a mutex? One mutex per session id. The whole request handler could be considered to be a critical section on a per session basis. ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
