Great, I just wonder how you evaluate the performance, how many concurrences? how many requests?
On Tuesday, September 9, 2014 11:25:04 PM UTC+8, dgrnbrg wrote: > > Announcing the release of Async Ring! Ring is a great foundation for > building HTTP servers in Clojure. However, Ring fails to solve many > problems that high-performance and transactional HTTP servers must solve: > > > - What does the server do when it can't handle the request rate? > - How can the server dedicate more or fewer resources to different > requests? > - How can long-running HTTP requests be easily developed, without > blocking threads? > > > Async Ring attempts to solve these problems by introducing a core.async > based API that is backwards compatible with Ring and popular Ring servers, > so that you don't need to rewrite your app to take advantage of these > techniques. > > > Async Ring comes with many features: > > - Ports of most ring middleware (just ask me and I'll port your > favorites!) > - Beauty, a compojure & clout compatible concurrent quality-of-server > router > - Integration with Jetty and Http-Kit, more coming > - Documentation and Examples > > > Take a look here: https://github.com/dgrnbrg/async-ring > > Feedback and pull requests welcome! > -- 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.
