> What about a case where you want to store the production files on some > external CDN? > > I guess that could be considered as part of the deployment process, done > separately through some additional script. But by keeping it all > "in-house", one could generate URLs that would work for both development > and production purposes. > > My latest experience with high throughput sites is that you can just serve this kind of assets through some HTTP reverse proxy cache like Varnish Cache. Separate CDNs are starting to shine if you want to serve non-cacheable resources, like millions of photos etc.
Anyway, I was thinking earlier about basing it on ring-spec protocol, so you've got me to consider the advantages again... I want to keep it practical - the features implemented now do not require a very high level of abstraction, so I don't want to get caught in a trap of overthinking it :). - Marcin > -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
