jvanasco wrote: > 1 - are you using sqlalchemy? if so , run stuff in dev and look for > issues with the sqlalchemy session thread ( it prints nice errors that > say "you're screwed!"
Nope, using a custom database layer called dbstore. > 2 - not sure how tg is handling this , but is tg calling an autolock on > the visit session? its entirely possible that you've got a race > condition going on because of ajax / json and timing. the way that > visit is currently implemented, its doing all of that identity stuff on > images , css , etc already. toss in json, and its a nightmare waiting > to happen. actually session expiry is handled by it's own independent thread which goes through and bumps the session expiration asynchronously through a shared Queue.Queue object, so it doesn't really matter how many requests come in. I still haven't been able to persue this much. Joseph By the way, I just bought a few squirrel calls. Hopefully I can lead them all away from my yard much like the fabled Piper of Hamlin. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
