jkbrzt/chat

A simple chat app created to experiment with Redis, Gevent, Flask & Server-Sent Events.

chat's Issues

Unexpected first data

When opening a browser, I found there was a line showing "1", which should not be there.

And in event_stream() function the print shows the following first data:

{'pattern': None, 'type': 'subscribe', 'channel': 'chat', 'data': 1L}

I'm new to this, and wandering what the 1L data is for. From my point of view, it should be empty.

How to handle client closed event?

It seems that the redis connection keeped when the page is closed. How to handle client closed event ?

decode byte string

The byte string should be decoded to utf-8, on a side note, the README should mention that the redis server needs to be started before the app is run.

How are client connection closes handled?

I'm using this model in a simple web application using a naive in-memory publish subscribe model I wrote. It's been incredibly useful, however, I've noticed (and I think I saw the same behavior when using redis) that this loop continues to run well after the client has disconnected. Have you experience and/or resolved that issue?

I'm thinking if I can get a handle to the client's socket I should be able to do a non-blocking test to see if it's still connected and break.

Edit: I was incorrect. Closing issue.

some clarification request

@jakubroztocil would you please provide some explanation regarding running this app through gunicorn + gevent workers?
In particular I can not understand how we're able to perform non-pending request to /stream with EventSource('/stream')? (In case of running app with gevent.pywsgi.WSGIServer I'll receive pending request for /stream but with gunicorn+gevent worker - 200 OK)

after running my browser loading large amount of time. How to overcome this problem.

I am running in localhost without using gunicorn