On 8/28/07, Graham Dumpleton <[EMAIL PROTECTED]> wrote: ... > Most importantly, you should rigorously test your application to > ensure that it is truly safe to use in a multithreaded web server. > Areas which I would suggest you look at closely are use of session > objects as these from memory do not provide a locking mechanism, and > so in an AJAX heavy application which issues lots of concurrent > requests and each handler for them wants to manipulate the same > session object, you might run into problems with the handlers and > sequencing of operations against the session object.
If your session usage follows this pattern, I'd recommend using something like PEAR: http://cheeseshop.python.org/pypi/pear/ It would not be difficult to modify django to support alternative session backends, similar to its cache and db abstractions. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
