I've posted a synopsis of this on the earlier referenced pylons thread to see what those guys have to say.
I don't think this is really an AJAX specific problem - although the asynchronous nature of AJAX means its more likely to occur. It seems to me that any http request can arrive concurrently at the web server from the same web browser sharing the same token or session -- unless the app server (pylons) in this instance serialized access to the controller under these circumstances then concurrent access to the same data model could easily occur. Perhaps SQLAlchemy could optionally cache any in-memory models and return the same instance to multiple threads so that local serialization on the model could take place? On Nov 2, 10:29 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > this would seem to me like it should be fixed at the ajax level, or > possibly the level of the webserver where it receives ajax events. > your ajax functionality constitutes a GUI, and most GUIs I've worked > with have a single "event queue" whereby all events are serialized > into a single stream. the nature of the XMLHttpRequest is > asynchronous so it seems like either your ajax library would have to > delay the second ajax request until the first one completes, or the > web server would have to enforce similar behavior (probably easier on > the ajax side).- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" 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/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
