snif VS Mongoose

The VESmail account manager guides though the setup process and provides the settings for your email client app to connect to the local VESmail app. For the convenience of the setup, the account manager suggests to use a trusted TLS connection via an end-to-end SNIF relay (https://snif.host), although a direct non-TLS connection to localhost (IMAP 7143, SMTP 7125) can be used instead.

That link (https://github.com/vesvault/snif/graphs/traffic) redirects to github.com because that is probably restricted to repository owners only. Try making the link https://github.com/vesvault/snif/

https://snif.host https://github.com/vesvault/snif

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/

If you are looking for something simple there is mongoose from cesanta, https://github.com/cesanta/mongoose