On Tuesday, April 29, 2014 3:29:26 PM UTC+2, tbc++ wrote: > > One of the biggest value propositions of Pedestal has always been that > it's the only Clojure web server library to support end-to-end async > operations. You can do things like have a handler return a core.async > channel, or pause/resume the entire web stack multiple times during a > single request. Other libraries may support async or streaming responses, > but none allow that level of control, so if you need that feature Pedestal > is there. >
Yes, it's a really cool feature. Unfortunately, I'm not going to need it! :-) > > Pedestal's routing stack is also data based, that's a pretty big deal if > you're used to debugging nested ring handlers that are instances of > functions. Data over code...that's the way I like it. > Yeah, that's what I thought as well. I also like that aproach much better. > > But yes, as a whole the entire Clojure ecosystem is built around small > composable libraries instead of a monolithic framework. Pick and choose and > build your own stack. > > That's what I'm trying to right now.... Did you use pedestal in a productive environment? Thanks, Bernhard -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
