3 ms·
From a cursory glance this seems to be a contender for libuv, so I would like to learn more about motivation for this project. Unfortunately, none is given, as
by tw061023 3y ago
From a cursory glance this seems to be a contender for libuv, so I would like to learn more about motivation for this project. Unfortunately, none is given, as well as why is it limited only to POSIX APIs.
- Zirias 3y agoIt certainly is not. Libuv (and friends) abstract platform-specific APIs like epoll (Linux), kqueue (FreeBSD), IOCP (Windows) etc, allowing to scale up to lots of concurrent clients/connections. I would recommend to use such a library for anything where you'd ever expect having to handle more than maybe 100 concurrent clients. This is a small and simple alternative (the only similarity is offering some event-based API) using nothing but POSIX. This allows to keep the code small and avoid conditional compilation (so far only used for the optional TLS support). You might want to use it when you want to write some "small" service for POSIX systems, and focus on your actual logic (e.g. your protocol implementation) instead of dealing with all the internals of handling sockets, name lookups, daemonizing, signals, threading where needed, and so on. A bit more info also here: https://groups.google.com/g/comp.unix.programmer/c/qsxDODLNeCY https://groups.google.com/g/comp.unix.programmer/c/qsxDODLNe...