BTW one more thing. If I am building anything serious. Anything which might be user facing and could potentially be used by even thousands of users, I would never consider Socket.IO. I just feel that it's a super hack which tries to do too many things with no guarantees on anything.
On Saturday, July 20, 2013 3:50:31 PM UTC-7, Anand Prakash wrote: > > This is an awesome discussion. Hope this leads to some good frameworks in > the community. > > I was looking at Socket.IO webpage and they seem to support the following: > Websocket, Adobe Flash Socket, AJAX long polling, AJAX multipart > streaming, Forever Iframe, JSONP polling. > > I understand some people are not comfortable with Websockets, because if > the early stage of this technology. > So there are two time of use-cases: > a. pseudo real time - e.g. chat apps - they should all be fine with > polling and long poll is an optimization. > b. real-time - e.g. multi player games, stock ticker etc - they would need > some kind of socket. > > To answer Sean's question - I understand there are benefits with the > socket.io client library. However you said that you do not want to go for > Websockets. So if that is the case, isn't AJAX long polling sufficient for > you. If that is the case then no client side library is required. You just > need to keep polling from the client. It's server's choice with it wants > return right away or implement long-poll. > I am new to this space - so just try to make sure if I am missing > something obvious. > > Thanks > Anand > > > On Friday, July 19, 2013 2:08:38 PM UTC-7, Christopher Martin wrote: >> >> Shameless plug: I recently shared a Clojure library for WebSockets and >> HTTP Kit: http://cljwamp.us >> >> It provides some features similar to Socket.IO in regards to >> pubsub/multiplexing events, and uses the WAMP spec which has several >> multi-platform options: http://wamp.ws/implementations >> >> While clj-wamp does not support long polling, a separate solution could >> potentially run along side it (since HTTP Kit itself supports long polling) >> though I haven't tried this yet. >> >> This library probably isn't a good option for Sean (the OP), but might be >> of interest for those looking into WebSockets with HTTP Kit. >> >> Cheers, >> ~Christopher Martin >> >> On Friday, July 19, 2013 1:33:51 PM UTC-4, c...@bitemyapp.com wrote: >>> >>> If you want something robust I'd recommend something like http-kit or >>> Netty on the backend + using websockets (and a shim) directly on the >>> frontend, or possibly browserchannel if you need to worry about firewalls >>> and ancient browsers. >>> >>> Socket.IO is a moving target intended for a single audience (not >>> multiplatform). It's not going to win you more than you'll pay in bugs and >>> performance issues in the long run. >>> >>> -- -- 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/groups/opt_out.
