3 ms·
I have a question - if you're only using sockets for push, why not use SSE instead? Or did you encounter serious issues with that?
by bphogan 11y ago
I have a question - if you're only using sockets for push, why not use SSE instead? Or did you encounter serious issues with that?
- jessaustin 11y agoI've had good results with SSE in just the situation that GP describes: client actions come in as POSTs and the results of those are communicated to everyone via SSE. In most cases we don't even care about the 204 or whatever. If it's not on SSE then it didn't happen. b^)
- bradgessler 11y agoSSE is fine except stupid Internet Explorer doesn't support it: http://caniuse.com/#feat=eventsource http://caniuse.com/#feat=eventsource A goal of Firehose is to have the fewest number of transports possible so the client doesn't have to spend much time negotiating the transport. I found WebSockets was more widely supported (http://caniuse.com/#feat=websockets http://caniuse.com/#feat=websockets) and HTTP long polling could take care of the rest. Before I built Firehose I looked at socket.io, which had a ton of transports, but found that it was too slow, flakey, and unpredictable for our needs.