Square Releases Open Source WebSocket Client for Objective-C

Is there any reason to use WebSockets on native apps other than if you want to share one server between native and web?

Thank god. I have worked extensively with cocoa-websocket and socketio-cocoa and they are a complete mess.<p>Square has done a lot for iOS open source, with their unit test framework and other libraries and now this.

So, following up on the link in another comment on this article [1] to socket.IO-objc [2], one goes through a few forks of cocoa-websocket [3,4,5] to arrive at zimt [6].<p>Are there reasons to use SocketRocket over these other libraries (either socket.IO-objc, or the various forked lineage of cocoa-websocket/zimt)?<p>(Also, to ask the question I always have to ask: is there a reason for a new library rather than contributing to one of the existing ones, possibly even helping Unitt support RFC6455?)<p>[1] <a href="http://news.ycombinator.com/item?id=3563527" rel="nofollow">http://news.ycombinator.com/item?id=3563527</a> [2] <a href="https://github.com/pkyeck/socket.IO-objc" rel="nofollow">https://github.com/pkyeck/socket.IO-objc</a> [3] <a href="https://github.com/samlown/cocoa-websocket" rel="nofollow">https://github.com/samlown/cocoa-websocket</a> [4] <a href="https://github.com/adamjernst/cocoa-websocket" rel="nofollow">https://github.com/adamjernst/cocoa-websocket</a> [5] <a href="https://github.com/erichocean/cocoa-websocket" rel="nofollow">https://github.com/erichocean/cocoa-websocket</a> [6] <a href="https://github.com/esad/zimt" rel="nofollow">https://github.com/esad/zimt</a>

We are currently using UnittWebSocketClient in our iOS app to communicate with a Tornado server:<p><a href="http://code.google.com/p/unitt/wiki/UnittWebSocketClient" rel="nofollow">http://code.google.com/p/unitt/wiki/UnittWebSocketClient</a><p>It has worked well so far, but I'm glad to see more activity in this area.

You guys are constantly pushing out cool stuff, just started using KIF and I really like it. Thanks for open sourcing guys!

Great to see this... I've been using libPusher, but it's specific to the Pusher service (which is actually pretty great).<p>Perhaps libPusher can just start using SocketRocket as a dependency and wrap it in Pusher-specific goodness...

If I'm using Socket.IO via an Obj-C lib, is there a point to taking a look at this? Should the Socket.IO community look at integrating this as the engine behind the client on Obj-C, or is there little/no benefit?

Does this get around the shitty reverse-proxies mobile providers set up that kill websocket connections?