stimer VS C++ Middleware Writer

Im plugging my own: https://github.com/deynh/stimer

cli timer. use it all the time. thought it was weird linux distros didn't come with something simple already (im aware you can make simple bash script if you wanted): https://github.com/deynh/stimer

Github

I use unique_ptr, but not as much as I used to. I've never used shared_ptr. This is my library that uses some C++ 2020 and 2017 features.

I started with Linux in the late 90s. I switched to FreeBSD around 2013 and returned to Linux a couple of years ago. Io_uring was the main reason I had to come back. At first I ported the back tier of my code generator back to Linux and then I ported the middle tier from being POSIX based to Linux.

Are there others that minimize multithreading and opt for multi-processing with single threaded processes? Call me a simpleton, but this approach eliminates some of the most difficult bugs by design. Here's an example of one of my single-threaded servers. The network io is asynchronous, but the file io is synchronous. Thanks

I've been working on this program for 13 years now. At one point it had 7 global variables and none of them were const. Now it has 4 global variables and 2 of them are const.

in one of my programs. I'm thinking about changing it to:

It's a merger of services and code generation: an on-line code generator that outputs low-level messaging and serialization code based on high-level input. It's implemented as a 3-tier system and uses output from the code generator in each tier. There's also a traditional library that's part of the repo.

Support for more data types for message lengths. Previously message lengths were always 4 bytes. I used this, for example, to reduce the size of the type used for message lengths between the front and middle tiers of the CMW from 4 bytes to 2 bytes.

More concretely, I use it to generate code that's used in each of the tiers mentioned above. The link is to one example of that.