Warren Smith wrote: > It occurs to me that a file-based session store may present > these problems > even with only a single app server and local filesystem, > since multiple > threads in the same app server could just as easily interact > in the ways > described. I see from the source of SessionFileStore that > this is a known > issue that has yet to be resolved.
That's why I always recommend using the Memory or Dynamic store :-) I wonder if any of the other app servers addresses this problem? mod_python now has sessions built in, and it handles requests in separate processes, so it seems like it would encounter this problem too. Another approach to the whole issue is to write your own session store, perhaps storing sessions in a SQL database that you might already be using anyhow. If you add a timestamp field to the table you are using to store sessions, you could then enforce a rule such as "last request wins" when determining whether to overwrite the session values. - Geoff ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
