I recently participated in the creation of a small websockets chat app. Prior to this my only experience with this great tech was from the perspective of the backend being implemented in a Spring stack that I saw at a conference. Well this app I helped create was done in node.js and everything seemed to be ready to go out the box with node.js where as a messaging layer needed/had to be added for websockets to work within the Spring stack.
Outside of Spring, do most implementations of websockets handle the messaging for you? I saw a Kaazing demo and it seemed they too would provide the messaging stack for you that node seems to just "do".
It really varies on a per implementation basis. Socket.io (the Node.js module for WebSockets) provides both the client and server libraries to make getting an application up and running pretty easy. However, it binds you to certain things like using JSON as your message structure. For certain applications the additional data needed to structure data as JSON can be too expensive. If you were creating a game, which typically involves lots of messages, you would want to send data in as light a wrapper as you can.
There are lots of client side libraries out there as well that will help to make the structuring of messages a bit easier when such a library isn't provided by your backend server.
Joined: Jul 17, 2002
Is there a simple listing of those various libraries somewhere that I could browse?
Joined: Mar 26, 2013
I am not aware of any well defined lists, but a quick github search shows a bunch of WebSocket libraries.
subject: Node.js websocket implementation vs others