wsServer VS libwebsockets

One great feature for me was being able to accept both WebSocket as well as raw TCP connections on the same port using libwebsockets, this is extremely easy and just required settings the flag LWS_SERVER_OPTION_FALLBACK_TO_RAW.

I encountered other hiccups. They are fully documented and completely valid, but were really confusing to me as a first-time user:

* Sending data requires a specific memory layout[2] – namely having to allocate memory for the websocket header youself before the actual message you want to send. This gave me confusing segfaults in the beginning.

* Sending data / responding to a client message will probably (but not always) fail when just naively using "lws_write()". To correctly send data you need to manually queue your message data, request the "ON_WRITABLE" callback[3] and only then actually send.

[1]: https://github.com/Theldus/wsServer

This is just the endemic result of C++ lacking a package manager.

Every library starts out small, adds its own vendored utilities, adds its own dependencies, and eventually becomes boost.

To be fair to this project, theyve worked quite hard to make the library consumable by others… but yes, its hard to look at the code like https://github.com/warmcat/libwebsockets/blob/50ba61082dc40b...

…and not go… really? As part of the core of libwebsocket?

When you read the justification it’s mostly “well we have a good framework now, so why not use it for other things too?”

C++ life.

/shrug

I'm trying to setup a project using libwebsockets.

Libwebsockets a powerful and lightweight pure C library\ (48 comments)

and how others have implemented the client