libmicrohttpd VS Mongoose

It's a C API (maybe there is a C++ wrapper) but libmicrohttpd is a pretty good choice.

Honestly, I think the HTTP server route would be what I'd recommend. Something like libmicrohttpd: https://www.gnu.org/software/libmicrohttpd/

A long time ago I had "fun" implementing all sorts of network protocols with such an event based library on C: https://github.com/cesanta/mongoose

I've found myself at this webpage multiple times while trying to minimize the complexity of APIs in my C projects.

My conclusion for now is that C coroutines are something to be left to the implementer. For example: Mongoose (https://github.com/cesanta/mongoose) uses event callbacks to deal with asynchronousness. It is much more pleasant to wrap a library like this in whatever thread/task primitives your system has rather than try to integrate the mythical cross-platform c couroutine.

I remember using mongoose 15 years back. Today i would have considered mongoose(10k+ stars) which is also a mature c/c++ web server[1] if not the licence.

https://github.com/cesanta/mongoose/tree/master/examples

Alternatives at the low to medium level of abstraction include civetweb and mongoose, which have a common ancestor. Both of these appear to be C rather than C++, but seem to be production quality and well-documented. Another C library is cpp-httplib, which is probably too low-level for me.

Since this is only going to be used internally would Mongoose be worth considering?

Here’s an example: https://mongoose.ws/