Socket.IO on iOS

Whenever I think of WebSockets/real-time I think of Socket.io but I would be interested to hear a response from the Socket.IO team in regards to Trello saying [0] they couldn't scale Socket.IO over 10K connections:

> We use a modified version* of the Socket.io client and server libraries that allows us to keep many thousands of open WebSockets on each of our servers at very little cost in terms of CPU or memory usage.

> * The Socket.io server currently has some problems with scaling up to more than 10K simultaneous client connections when using multiple processes and the Redis store, and the client has some issues that can cause it to open multiple connections to the same server, or not know that its connection has been severed. There are some issues with submitting our fixes (hacks!) back to the project – in many cases they only work with WebSockets (the only Socket.io transport we use). We are working to get those changes which are fit for general consumption ready to submit back to the project.

I'd be interested to hear if those "hacks" got merged in or fixed some other way. Of course most of us aren't dealing with 10K simultaneous connections and Socket.IO is awesome so this is in no way a warning to keep away from it, I'm just interested.

[0] http://blog.fogcreek.com/the-trello-tech-stack/#asterisk

So, is this a way to mesh native and web apps together?

For example, I want to create a multi-player game and demo it to an audience of 500. I get up on stage and ask them to go to a URL to join in on the fun while I'm using the native app to control the experience.

Right now our BlueTooth Audio like web framework (http://SpeakerBlast.com) uses Socket.IO and we've had a few clients request a native & web experience for their events.

Stream all the things!