On Sat, Apr 11, 2015 at 10:46 AM, Malcolm Sparks <malc...@juxt.pro> > > So, in summary, I think it would be useful to have a single 'default' > routing library in Clojure that supported isomorphism and was built on > protocols, as a minimum. Now that Clojure is attracting so many new users, > it would be great to discuss the outstanding differences between all the > routing libraries and try to drive some consensus as to what a combined > library would include. >
I'm on board with most of this post (and the Bidi approach in particular), I'm not sure consensus is necessary but I'll throw in my 2 cents. - Please, no more defroute etc macros - Routing should be composable. I want to take some routes and just plug them in at some level of my existing hierarchy. - Middleware should be decoupled from the routes as much as possible. The process for associating middleware to the request should be parallel/complementary to resolving the resource. Maybe "middleware" is not the best concept to begin with. -- 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/d/optout.
