By scalable, I mean that the capacity of the application can be increased by adding resources. Conjure and Compojure are scalable under this definition.
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. The Google Servlet Engine is an example of a server that allows thread sharing without an event based model. A request handler can detach from the thread (http://code.google.com/p/opengse/source/browse/trunk/ transports/nio/java/com/google/opengse/core/HttpConnection.java#291) and reattach later (http://code.google.com/p/opengse/source/browse/ trunk/transports/nio/java/com/google/opengse/core/ HttpConnection.java#324). The Google Servlet Engine is used by Gmail Chat, an application with a very large number of concurrent connections. The proposed extension to Ring for Websockets (http:// groups.google.com/group/ring-clojure/browse_thread/thread/ 849390e7e65d3f92) is another example where threads can be shared between requests without an event based programming model like node.js. On Jul 20, 8:20 am, Peter Schuller <peter.schul...@infidyne.com> wrote: > > You can build a scalable app with Conjure on Jetty. You don't need an > > evented server like Aleph or node.js to build a scalable app. > > Depends on what you mean by scalable. If you want to keep 250 000 > concurrent mostly idle connections, you'll likely want to be event > based. > > -- > / 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
