Back-to-back event receiving with gevent about flask-uwsgi-websocket HOT 4 OPEN

I dug into this a bit more. There seem to be a couple issues doing on here:

1. Suppose that client.fd receives 200 bytes. As long as no bytes have been read, select(client.fd, [], timeout) returns instantly. As soon as a byte has been read, select(client.fd, [], timeout) takes timeout to return -- regardless of whether 1 or 200 bytes have been read.
2. Some browsers seem to send back-to-back empty messages, which all need to get read from the system. If empty messages are left unread, they seem to prevent PONG messages from being sent (I'm not sure in which direction), which causes the socket to timeout. I ended up with this implementation:

            elif recv_event.is_set():
                recv_event.clear()
                try:
                    message = True
                    while message:
                        message = uwsgi.websocket_recv_nb()
                        recv_queue.put(message)
                    listening = spawn(listener, client)
                except IOError:
                    client.connected = False

It ends up writing an empty message for every event, but better than the alternatives.

from flask-uwsgi-websocket.

That seems like a nice solution, would you like to send a PR?

from flask-uwsgi-websocket.

I will; it may be a couple days.

from flask-uwsgi-websocket.

Created #48

from flask-uwsgi-websocket.