uSockets
uSockets copied to clipboard
Miniscule cross-platform eventing, networking & crypto for async applications
Is there a reason there's no `us_socket_remote_port` to sit alongside `us_socket_remote_address`? Perhaps I'm missing something and there's another way to obtain that data.
dh_params_file_name option in openssl.c is deprecated and needs to be rewritten for OpenSSL 3.0 support.
clang-11 complains: ``` ===> Testing for usockets-0.8.0 cd /disk-samsung/freebsd-ports/net/usockets/work/uSockets-0.8.0 && cc -o test tests/sni_test.c /disk-samsung/freebsd-ports/net/usockets/work/stage/usr/local/lib/libuSockets.so tests/sni_test.c:1:8: error: expected identifier or '(' extern "C" { ^ tests/sni_test.c:22:14: warning: implicit declaration of...
* uSockets/src/internal/networking/bsd.h \#include "libusockets.h" for LIBUS_SOCKET_DESCRIPTOR
TCP, TLS, QUIC as enum protocol
_t postfix should be typedefed
does not work on Windows for some reason but works on Linux, maybe something with `us_socket_shutdown_read`, I guess windows is not really supported because no multi-thread support so just use...
Various threading features are required. Reuse port, master listener & slave worker, etc.
We need to have a libFuzzer mock for SSL so that we can efficiently fuzz the SSL support.