If notifications only go one way, server side events should also be considered.
...but I don't remember the advantages anymore :)
Have a look at this [0]:
- Automatic reconnection
- Event ids
- Straightforward protocol built on plain old HTTP
[0] http://www.html5rocks.com/en/tutorials/eventsource/basics/
Re:You might not need a WebSocket
by manishsharan on Thursday July 10, 2014 @01:50PM
(#8016046)
Once you introduce a websocket on your html simple page app, it makes sense to send all the user/browser side events to server over the websocket as well. Use socket.io like aggressive websocket connectivity tests and failover to normal REST ajax.
We also support long polling etc. but websocket servers are idling while our polling/push servers are at higher cpu utilization with comparatively lower loads.