Re:Rails in Realtime - How LayerVault updates every page in ...
by damncabbage on Wednesday September 05, 2012 @08:22PM
(#4482232)
Especially since pusher is a third party service and it's probably using
(or is able to use) websockets as a transport for that push anyway?
Pusher.com's page title is "HTML5 WebSocket Powered Realtime Messaging Service", no less.
Re:Rails in Realtime - How LayerVault updates every page in ...
by 1qaz2wsx3edc on Wednesday September 05, 2012 @08:25PM
(#4482246)
Let me clarify, you can use pusher, or something like firehose.io.
Pusher uses a web socket. Pusher is cheaper when comparing against running our own dumb pub/sub server.
Rails 4 will support SSE, however we're not riding that edge as there were existing solutions to the problem.
-
I think this covers most realtime problems without having to code that much, let alone a secondary server/service to handle the problem, we outsourced it, were happy.
Re:Rails in Realtime - How LayerVault updates every page in ...
by drivebyacct2 on Wednesday September 05, 2012 @08:53PM
(#4482322)
Hm, I guess I'm blessed with a library for it, but I'm using my own WebSocket server with no sweat right now.
Re:Rails in Realtime - How LayerVault updates every page in ...
by dylanvee on Thursday September 06, 2012 @02:09AM
(#4483031)
Actually, SSE is a better fit here: it works in many more browsers than WebSockets when you count the existence of SSE polyfills, and you don't need the bidirectionality of WebSockets here.
Sure, you can use Sever-Sent-Events, but a Websocket would be sufficient too (and probably works in more places, no less).