mio VS Mongoose

As simple and clean example you can see https://github.com/mandreyel/mio readme.md

I loaded a 7Gb file into a memory map using the mio header file. The mmap variable is a char* array. I used a short file since this is my first time attempting a memory mapped file. This is the text2.txt file

I am using this mio header file and attempting to read in a 7GB file. This is taking a long time to execute so I stop the execution. I am reading in a small file just to test this out.

A great fellow redditor showed me this memory mapping header file to read in large files. This is how I am using it with a syntax error.

I would memory map it. Use this lib: https://github.com/mandreyel/mio

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