Provide info whether websocket_recv'ed message is binary or not

[venthur]

Hi,

this bug is related to #1160 (autobahn testsuite failing for fragmented messages). For the echoserver provided in #1160 the testsuite fails also for a lot of unicode-, text- and binary related messages. The problem is, that the server has to guess wether the client sent binary or not. My solution is to try to decode the message and catch any UnicodeDecodeErrors and assume its binary then. But websocket_recv should really provide the info weather the message is binary or not. Since this distinction is made somewhere in the websocket protocol you can just forward this information. Otherwise there is no reliable way to guess weather a message is binary or text.

The autobahn websocket implementation provides this message is_binary along with the message.

[Darvame]

forward op codes: 0x1 (text) and 0x2 (binary), and doing something with op code 0x0 (continuation)

[methane]

text message must be utf-8.
So websocket_recv() can return unicode for text message.

[Darvame]

@methane he is talking about op codes of websocket frame

[danlg]

@miguelgrinberg says miguelgrinberg/python-engineio#275 is due to a bug in uwsgi code regarding the improper support of binary data. Do you agree @xrmx @unbit?

[danlg]

hello @xrmx @unbit?