2 suggestions -

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!"

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.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to