Tatsuhiro Tsujikawa

Hm, it is already quoted. Probably, pkg-config is missing. Could you check that pkg-config is installed on your system?

It is very strange. It works for me for years. We have experimental cmake support. Probably it could work.

aclocal.m4 included in wslay distribution includes definition of PKG_PROG_PKG_CONFIG, so it should work. It is true that pkg-config binary is required. If you are compiling from git, then yes, you...

Finally, I made a progress on this. I added `wslay_event_write` which writes pending messages to a given buffer instead of calling send_callback. This avoids WSLAY_MSG_MORE and small packet write. Still...

Reading the source code shows there is no way to send message to peer inside wslay_event_queue_msg. It just adds new message into the internal queue.

Check out https://github.com/tatsuhiro-t/wslay/blob/6abacc1da10344d7d7b13c21edc76fcdf587de0c/examples/testclient.cc It is design decision to make wslay know only about WebSocket framing layer. It allows for existing HTTP implementation to integrate wslay easily. Implementing HTTP upgrade for...

Thank you for the patches. While I understand the usefulness of cmake, but I want to keep autotools files. Also I think storing libraries source files in lib folder is...

I am OK to add cmake support. But I'd like to keep autotools, just like curl project does. I'm not fully determined to get rid of autotools yet. Choosing source...

@wonder-mice yes. We accept cmake support patch, with the condition that autotools support is still in tact.

Changing callback signature will break API compatibility. I think using [wslay_event_set_error()](http://wslay.sourceforge.net/man/wslay_event_set_error.html#c.wslay_event_set_error) can tell the library to return immediately. The existing use of wslay_event_set_error() is described in http://wslay.sourceforge.net/man/wslay_event_context_server_init.html. For example, we...