At 10:24 AM 12/10/01 -0800, Chuck Esterbrook wrote: >On Monday 10 December 2001 06:14 am, Geoffrey Talvola wrote: > > File also has some tricky concurrency issues, mentioned in the > > comments to SessionFileStore.__setitem__(). If two servlets > > simultaneously modify the session, one change wins and the other > > change is lost. Whereas Memory works perfectly and is significantly > > faster, especially if you're storing lots of data in sessions. > > > > I vote for making Memory the default until we fix the Dynamic store. > > And we ought to document the problems with the File store somewhere > > other than in the comments. > >I thought Memory didn't work with OneShot very well and therefore was >poor for development. Is that no longer true? > >-Chuck
Hmmm, I guess you're right. Looking at SessionMemoryStore.py, it appears that it doesn't load and save session data if the appserver is non-persistent. If we removed the checks of isPersistent in SessionMemoryStore.py, I think it would work fine with OneShot.cgi. I'm not really sure why those checks are there -- all they seem to do is make it impossible to use the Memory store with OneShot.cgi. -- - Geoff Talvola [EMAIL PROTECTED] _______________________________________________ Webware-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-devel
