Tatsuhiro Tsujikawa

Yeah, something like that. I prefer adding new enum value to wslay_error, and check the desired value explicitly here.

Thank you. We got merge conflict here. Could you review the change?

It is not fragmented by WS library at least. Because the wslay_frame_recv() returns only available payload in the received buffer, application may have to call wslay_frame_recv() several times. If that...

This depends on the point of view. The wslay_frame_recv() is a library API and is not a function that returns the actual WebSocket frame. That said, I'm open to set...

I think working well in linux is just coincidence. wslay has no mutex inside it, and using wslay_event_context_ptr from multiple threads is unsafe, and must be avoided. If some work...

wslay_event_context must not be used by multiple thread at the same time. If you'd like to use it from multiple thread, use mutex around the calls.

Chrome refuses to connect wss if the server uses self-signed certificate. To workaround this, before connecting the server, open the tab with URI with wss replaced with https. Chrome shows...

We use wslay as WebSocket backend since last summer. It works great. Here is the relevant piece of code: https://github.com/tatsuhiro-t/aria2/blob/master/src/WebSocketSession.cc Note that the SSL/TLS library backend is abstracted under SocketCore.

What error message did you get when you do this?

arg->msg is const pointer to uint8_t, so you cannot modify the pointed region directly. arg is self const pointer. Instead, create your own buffer, and write your data into it,...