Conversation
|
Sorry for the lack on feedback and thanks for the support and for the code contribution. I think the main reason I cannot go with this change as is currently wired is that it uses a custom version/configuration of libmicrohttpd without making it optional. I think that needs to be solved before we can merge this change - many consumers of the library use libmicrohttpd as installed by their OSes and this would practically break their builds entirely. |
Thanks for the quick reply. |
|
Whilst I appreciate concerns for the existing user base, change is inevitable. It is called progress. Existing projects relying on libmicrohttpd would need to update / re-compile their code. Just like all the other open-source projects do when there are API breaks in their codebases and / or dependencies. I've been a faithful libmicrohttpd user for nearly 10 years. It is just great, the API is ergonomic, the |
Hi are there any plans to provide a C-only WebSocket example? My project uses FORTRAN and pure C with no C++ whatsoever. |
|
libmicrohttpd removed microhttpd_ws in September 2025 after release v1.0.2 … |
|
@LeSpocky that's really a pity. |
|
The upgrade handling is still in place. I guess you would just need to handle the socket you get with some other code. Will look into that later. |
|
That's great to hear. This is what I am already doing, handling the WebSocket messages (a TCP connection) in a custom C code after the initial upgrade. |
|
Here is some sample code: |
Issue or RFC Endorsed by Maintainers
Enable WebSockets #20.
Description of the Change
Added websocket support.
Alternate Designs
Extending the existing
http_resourceclass was considered, but rejected in favor of a new class and multiple inheritance.Possible Drawbacks
libmicrohttpserver does not yet compile the websocket-support by default. It must be done by building
libmicrohttpd/src/microhttpd_ws.Verification Process
Created and tested an example application
hello_world_websocket.cppunder Ubuntu 20.04.Release Notes
Added support for websockets.