#6195: Allow caching of the javascript translation library by the client browser
-------------------------------------------+--------------------------------
Reporter: jdetaeye | Owner: nobody
Status: new | Milestone:
Component: Internationalization | Version: SVN
Resolution: | Keywords: i18 javascript
Stage: Someday/Maybe | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 1 |
-------------------------------------------+--------------------------------
Comment (by ramiro):
Replying to [ticket:6195 jdetaeye]:
> Caveats:
>
> * If a user switches languages on the fly or uses multiple languages at
the same time, the javascript library isn't updated automatically to the
new language. (A more advanced patch could use the Etag header to cover
this case)
>
Replying to [comment:3 mtredinnick]:
> You certainly have to work around the first problem you mention. If the
user changes the language, the translations they see must all be updated
correctly.
#5691 proposes adding the language name to the cache key.
--
Ticket URL: <http://code.djangoproject.com/ticket/6195#comment:5>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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/django-updates?hl=en.
