Thank you all for the input, it has made me understand some new things. I find node.js push for NIO as the de-facto mode of existence for web apps interesting, and I was trying to have my cake and eat it too. JS programming just doesn't look all that appealing.
- V On Jul 20, 1:46 pm, Peter Schuller <peter.schul...@infidyne.com> wrote: > > If a web app does have a large number of concurrent requests, then you > > need a model where requests share threads. A full blown event based > > programming model is not required for thread sharing. > > Of course you can mix asynch and threaded at your leasure, with > appropriate interfaces in between; but it still boils down to limiting > the thread-wise concurrency and relying on evented I/O for the bits > that require that particular form of scalability. > > Don't get me wrong, I really dislike writing callback based asynch I/O > code, but since the OP specifically asked for a comparison with > node.js it's relevant to point out that no, clojure doesn't inherently > get you massive concurrency even if you can most definitely do > threading/asynch mixing with clojure like with most languages. > > -- > / Peter Schuller -- 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
