On May 28, 2009, at 5:53 AM, Chris Withers wrote: > Just about finished reading the Pylons book now and left wondering > what > the Pylons story is on transactional isolation? > > I'm guessing that the session maker user with the SQLAlchemy > integration > will give isolation sessions per thread and so things should be fine > on > that front, but a lot of the examples use writing to files on disk and > there seem to a be a lot of possible thread/process related problems > to > the techniques used. Am I missing something or do these book examples > need big warning disclaimers?
SQLAlchemy handles its transactions in a thread-safe manner. Not sure what examples you're referring to, as I haven't read the book myself. I'd guess they need a warning if they're accessing the filesystem in an unsafe manner. > Also, where/how does Beaker store its session data in such a way that > multi-thread/process apps aren't a problem? Beaker uses a multiple-reader/single-writer locking system to allow multiple threads to read the session at once, but locks so that only one can write the session at a time. Cheers, Ben --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
