Hi, I want to put my javascript translation catalogs in a CDN, considering the following points:
* In all the calls my app does to javascript_catalog(), the only thing which can influence the result is the active language. So there is exactly one possible javascript catalog per language I support. * I know the django admin has its own calls to javascript_catalog(), I don't care about not keeping those in the CDN. * My app always knows its own current version, and the active language for a request. Therefore, I could just reference, from my templates, a file in the CDN that has the app version and active language in the filename and then always get the correct version, if only that file was available. My hacky way to support this is, I wrote a small static files finder that simply produces one file per supported language by calling the javascript_catalog view offline, while running collectstatic. And when deploying I can sync those to the CDN along with the rest of the static files. I know static files finders are considered a private interface, I'm fine with knowing this and maintaining this part of my code whenever I update Django and in the worst case I can always fall back to the normal way of doing things. I've tried it and it works well so far. So... is this a dumb idea? Daniel Izquierdo -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
