On Mon, 15 Aug 2005 15:46:19 -0500, "Ian Bicking" <[EMAIL PROTECTED]> said: > > That is a design decision which not all frameworks (or other consumers > > of our session lib) might share. Apparently, given the current Python > > session modules out there, it's common to survive without caring? I know > > Mike Robinson has worked many long nights trying to make a session > > module for CherryPy which can consistently pass simple hit-counter > > tests. ;) Personally, I'd like to pursue an MROW solution. > > In practice race conditions are very uncommon. Simultaneous requests > from the same session are uncommon, since what few simultaneous requests > that occur are likely to be for boring resources like images. If you > have an image bug on a page that also writes the session, maybe you'd > have a problem. I'd be okay saying "don't do that" because usually > people don't do that, so it's not very compelling.
I wouldn't be okay with non-threadsafe sessions. -Jonathan _______________________________________________ Web-SIG mailing list Web-SIG@python.org Web SIG: http://www.python.org/sigs/web-sig Unsubscribe: http://mail.python.org/mailman/options/web-sig/archive%40mail-archive.com
