Thanks both. On 13 October 2014 04:27, Dom Kiva-Meyer <li...@domkm.com> wrote:
> Thanks for the experience reports, Dylan! > > Colin, Silk is Ring-compatible and meant to be used as a single > replacement for both Compojure and Secretary (or any other server/browser > routing combination with incompatible syntax and semantics). But, as Dylan > said, it's totally fine to use it in conjunction with Compojure instead of > replacement. Silk should also work fine with all Ring middleware. > In the next version, Silk will have a more familiar and mostly > Compojure-compatible syntax for defining routes. My hope is that this will > make it easier to translate Compojure examples/code to Silk. > > > On Fri, Oct 10, 2014 at 9:25 AM, Dylan Butman <dbut...@gmail.com> wrote: > >> I’ve been using silk in conduction with compojure. Most middleware aren’t >> compojure specific, but I’ve just found it easier to stick with base level >> compojure routes and then pass uris to silk for pattern matching. This is >> mostly because there is such a wealth of documentation and examples to draw >> from with compojure. For example, session management, login flows with >> friends, etc have already been solved and there is plenty of code to strip. >> Silk wouldn’t complicated them (in some cases it might simplify), but when >> the wheel rolls, push it. >> >> >> I’ve been approaching silk solely as a library for pattern matching >> within the specific domain of urls, which it does very cleanly. More >> importantly, it’s currently the only one that does it in both clojure and >> clojurescript, which makes it possible to have the same routing code used >> on client and server, which is necessary if you want to do server >> rendering, or more complicated websocket updates. >> >> -- >> Note that posts from new members are moderated - please be patient with >> your first post. >> --- >> You received this message because you are subscribed to the Google Groups >> "ClojureScript" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojurescript+unsubscr...@googlegroups.com. >> To post to this group, send email to clojurescr...@googlegroups.com. >> Visit this group at http://groups.google.com/group/clojurescript. >> > > -- > 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 a topic in the > Google Groups "Clojure" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/clojure/D95anPmhNhU/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > clojure+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- 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.
