On Wed, 2008-10-15 at 13:20 +0530, Amit Upadhyay wrote: > [So far using non > db based session backend, and allowing delete for auth_messages from > "GET machines" and living with "a message appears more than once" is > what I am doing].
By the way, for something like sessions, the scaling solution is not to use server-side storage at all for the session data. Typically sessions don't actually hold that much data and even in cases like, say, a checkout trolley, you could push the data into a session-correlated table, rather than the session object itself. So client-side sessions (signed cookies, etc) are the way to go in that case. Regards, Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
