uSockets
uSockets copied to clipboard
Miniscule cross-platform eventing, networking & crypto for async applications
hi, Currently uWebSockets and its dependency "uSockets" define a macro "WIN32_EXPORT" in header file "libusockets.h", as the following. So all uSockets api functions and a uWebSockets class named "struct WIN32_EXPORT...
I'm not sure if these arguments are implicitly zero when omitted for others, but without providing or deleting the parameters the examples fail to build with my toolchain.
First step to add unix domain socket support for uWebSockets. According to our [previous discussion](https://github.com/uNetworking/uWebSockets/discussions/1438#discussioncomment-2570789), this PR add unix sockets supports both server(listen) and client(connect) side, it also compiles successfully...
Allows listening to unix domain sockets over tcp. Does not implement connecting to a unix domain socket as a client or udp. I happened to want this for a project...
Add new function us_socket_transfer by extracting existing code for handling accepted sockets, and calling it from its former location. The new function can now be used to hand off a...
darwin has a number of i/o functions that won't return [EINTR](https://www.gnu.org/software/libc/manual/html_node/Interrupted-Primitives.html) This line: https://github.com/uNetworking/uSockets/blob/eab7df550a7ebc631e2adcff8b7364481661e879/src/bsd.c#L67 Could be: ```c int ret = sendto$NOCANCEL(fd, packet_buffer->buf[i], packet_buffer->len[i], flags, (struct sockaddr *)&packet_buffer->addr[i], sizeof(struct sockaddr_in)); ```...
For a project I've just been working on, I needed to be able to transfer in a socket that I created outside of uWebSockets/uSockets. I modified loop.c by moving the...
Just reporting WOLFSSL is broken on 0.5.0 as well. LOG: cc -march=native -O2 -pipe -fno-plt -ftree-vectorize -DLIBUS_USE_WOLFSSL -I/usr/local/include -std=c11 -Isrc -flto -O3 -c src/*.c src/eventing/*.c src/crypto/*.c In file included from...
Note to self and whomever is interested; It looks like uSockets is going to implement all 4 protocols - why? Because QUIC _definitely_ belongs here, so why have HTTP3 in...
It is a golden opportunity to create reliable benchmarking of quic stacks. They rely on nothing but udp i/o.