Hi,

I'd like to make a proposal of changing the way that current language is 
stored, at least, making this changeable by settings.
The problem is that even for non-logged users their language is stored in 
session (if it's supported or in the cookie otherwise).
That creates a session for every client, which makes serving static (ofc I 
mean static, but not media) content through an upstream
cache (such as Squid) really inefficient. I suppose selected language is not 
that secret to protect it by storing in session,
and cookie is just ok. For cookie-varying cache it's a huge difference.

I may be very wrong - in that case please just tell me what design concept 
lays behind this system. ;)

-- 
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 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Reply via email to