server-sent-events

The below has given an answer using node.js. How to close a "Server-Sent Events"-connection on the server? However, how to do the same thing in python Flask? Well, it depends on the architecture of your app. Let me show you an example (see this code at https://github.com/jkbr/chat/blob/master/app.py ): def event_stream(): pubsub = red.pubsub() pubsub.subscribe('chat') for message in pubsub.listen(): print message yield 'data: %s\n\n' % message['data'] @app.route('/stream') def stream(): return flask.Response(event_stream(), mimetype="text/event-stream") Flask asks a new message to Redis

I'm working on a project utilizing Server-Sent-Events and have just run into something interesting: connection loss is handled differently between Chrome and Firefox. On Chrome 35 or Opera 22, if you lose your connection to the server, it will try to reconnect indefinitely every few seconds until it succeeds. On Firefox 30, on the other hand, it will only try once and then you have to either refresh the page or handle the error event raised and manually reconnect. I much prefer the way Chrome or Opera does it, but reading http://www.w3.org/TR/2012/WD-eventsource-20120426/#processing-model , it

I have a web application that listens for Server Sent Events. While I was working and testing with multiple windows open, things were not working and I banged my head for several times looking in the wrong direction: eventually, I realized that the problem was concurrent connections. However I was testing a very limited number and even if I am running the test on Apache (I know, I should use node). I then, switched browser and noticed something really interesting: apparently Chrome limits Server Sent Events connections to 4-5, while Opera doesn't. Firefox, on the other hand, after 4-5

I am trying to setup message notifications in an Angular/Rails app. When the user logs in, I want to open a SSE connection which will subscribe to a Redis stream and push an alert to the client when the user gets a new message. I have my SSE setup and working, but cannot figure out a way to reliably close the SSE connection when a user logs out. I am trying to build a service to handle SSE opening and closing: angular.module('messagesApp') .factory('StreamHandler', function(CookieHandler, MessageStream){ var StreamHandler = { set: function(){ var user user = CookieHandler.get(); MessageStream

I am writing a webapp, using express.js. My webapp achieves the following User posts 100 json objects Each json object is processed via a service call Once the service call is completed, a session variable is incremented On incrementation of the session variable, a server side event must be sent to the client to update the progress bar How do i achieve listening on a session variable change to trigger a server-sent event? Listening to a variable change is not the only solution I seek? I need to achieve sending a server-sent event once a JSON object is processed. Any appropriate suggestion is

I have a usecase for which I would like to know if HTML5's Server-sent-Events is suitable. Multiple clients (Javascript+HTML5 browsers) connect to the web server (with a Java EE backend). Each client could be looking at a different view at any time, depending on what is their object of interest. My Question is: How to keep multiple clients (on different views) up-to-date on the updates happening on the server-side, without flooding all clients with all updates on all views ? Important points that I need to consider are: Many clients might be interested in the same events. If two clients are