If you need scalability, two phase connect might be necessary. 1. Resolve a server name which client should be connected to. If a client need to be connected to specific resource (chat room etc) consistent hashing is useful. http://nakkaya.com/2010/05/05/consistent-hashing-with-clojure/ 2. Connect.
On 2月2日, 午前7:05, blais <goo...@furius.ca> wrote: > Hi Clojurians, > > Does anyone have experience with serving WebSockets from Clojure, in > particular w.r.t. scalability? I'm evaluating server-side options for > handling a large number of simultaneous web clients (>100) and > wondering how well this scales. > > I already hooked up Clojure to Netty and built a simple test > application. I think I'll write some stress tests, but any feedback > regarding how well this could scale, possible roadblocks, or > experience reports would be appreciated and informative. > > Thanks, -- 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