Native Socket.IO and Android(socket.io)
socket.io
Native Socket.IO and Android
http://socket.io/blog/native-socket-io-and-android/
12 comments
I've been using Socket.IO on Android for 6+ months now to do real-time communication with our backend, and it works well for our needs. I was happy to see a well-written Android client come along with Socket.IO v1.0. The namespacing functionality makes it super easy to send different messages to different groups of clients.
This is pretty cool.
On a similar note, anyone know of equivalent options for iOS? I see a few open source implementations, but none that are actively developed. There's SocketRocket, but that's just vanilla WebSockets.
On a similar note, anyone know of equivalent options for iOS? I see a few open source implementations, but none that are actively developed. There's SocketRocket, but that's just vanilla WebSockets.
There is a similar Socket.IO library for iOS hidden within the FAQ.
http://socket.io/docs/faq/
http://socket.io/docs/faq/
Wow.
I've just had a heated debate about this at work. I think it's pretty cool, my colleague thinks it's the worst idea ever.
Does this actually work in the real world? What if i'm moving?
I've just had a heated debate about this at work. I think it's pretty cool, my colleague thinks it's the worst idea ever.
Does this actually work in the real world? What if i'm moving?
What are the opposing viewpoints?
Since almost all platforms support Websocket, is it necessary to use Socket.io?
On top of its transport layer abstraction, socket.io adds various useful features including events, rooms, namespacing, efficient/convenient (de)serialization and network callbacks. I've been using it in websockets-only mode for various projects, because I don't care for slower / less reliable transports but still want the extra features.
While Websocket has good supports by browsers, it doesn't always handle switching between networks correctly, also, some networks disallow Websockets altogether, or drop websocket connections over HTTP, but not over HTTPS.
Socket.io (especially > 1.0) solves these issues with a layer by having smart reconnection mechanisms and starts by connecting over plain old HTTP longpolling, and upgrades the connection to use websockets if they're available and work.
Socket.io (especially > 1.0) solves these issues with a layer by having smart reconnection mechanisms and starts by connecting over plain old HTTP longpolling, and upgrades the connection to use websockets if they're available and work.
It's not. There's an under-appreciated NPM module which is/was shared by Socket.IO that only handles the low-level WebSocket protocol for NodeJS:
https://www.npmjs.com/package/websocket.io
You can use that, and the built-in WebSocket object in modern browsers.
https://www.npmjs.com/package/websocket.io
You can use that, and the built-in WebSocket object in modern browsers.
Grande Guille!