Hancock, David wrote: > New question, similar to the old question: Are there some > semantic differences in how in-memory sessions > are handled vs. file-based sessions?
Yes, there are important differences between the two if there are multiple servlets simultaneously accessing the same session. With in-memory sessions, one servlet immediately sees the changes made by another servlet since there is only one copy of the session object, shared among all servlets. With file-based sessions, however, each servlet has a _separate_ copy of the session object loaded from the pickle on disk as needed, and that data is pickled back to disk at the end of the transaction, WIPING OUT ANY CHANGES that were made in the session by another servlet. This can lead to unpredicable buggy behavior if you are not careful. I feel that the Memory session store leads to more predictable behavior, so that's what I would recommend using in most cases. - Geoff ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
