The new cache backend for sessions in 1.1 looks very promising, I just have a quick question.
When running in a cluster, we need to make sure that if a user hops from one server to another that the session data remains in sync between the requests. I know that with the db backend the response for the first request won't be returned until the session data has been written successfully - which means there are no sync issues. Is the same true of the memcached-based backend? i.e is the response delayed until there is some confirmation that the cache has been written to? Regards, Andrew Ingram --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
