On 16 November 2013 17:55, Marcin Skotniczny <cosmi.co...@gmail.com> wrote:
> Cornet works on lower layer and does not use ring-spec or HTTP. All the > functions and middleware in Cornet take path as String and return > java.net.URL (either "file:/..." or "jar:file:/") [as a side note: at some > point I want it to be able to return data as InputStream or String instead > of urls. ] For integrating with ring, there's wrap-url-response function > that creates Compojure's (GET "/*"...) route out of Cornet function. > Doesn't this approach risk unnecessary repetition? If someone writes some caching middleware, or middleware that optimises Javascript, or whatever else, it's not compatible with the new abstraction you've introduced. It would be difficult for me to use Cornet in my own projects, for instance, because I'd have to maintain two separate systems for caching compiled resources. - James -- -- 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.
