relic_native 2.0.0-rc.7

A Relic adapter backed by a Zig HTTP server on native I/O threads.

2.0.0-rc.7

• A connection with nothing to read holds no task and no buffers. Once it has waited a second for a request, a WebSocket frame or a hijacked connection's bytes, it gives its buffers back, its task ends, and a poll of the socket starts one again. A WebSocket or hijacked connection starts that way. An idle WebSocket takes about 3 KiB where it took 29, and 15 KiB over TLS
• A connection's read, write, head and body buffers come from a pool of the reactor, which frees the ones no connection needed for a second. Before, they were on the task's stack for as long as the connection lived
• A TLS connection leaves its ciphertext buffers unwritten when it opens. Before, it wrote all 33 KiB of them, used or not
• The sweeper runs once a second on a server with no timeout set. Before, such a server had none
• The waiter thread reads the loop's host handle once, when the reactor starts. Before, each wait read loop state that a tick writes, which ThreadSanitizer reported in a debug build

2.0.0-rc.6

• A close in any Connection line closes the connection after the response, whatever else the lines list. Before, only the last line counted, and an HTTP/1.0 request kept its connection on a keep-alive beside a close
• An HTTP/1.0 request with Transfer-Encoding closes its connection after the response, even with keep-alive
• A tick that brings new exchanges and events together loses none of them. rc.5 read the events into the buffer that held the new exchanges, so concurrent requests and WebSocket upgrades could stall
• An error thrown while the adapter hands a tick's events and exchanges to Dart, as by a response body's own stream subscription or by the exchange sink, leaves the reactor running. Before, it stopped every connection on the isolate
• A WebSocket upgrade request with a chunked body leaves the reactor running. Before, the body's chunks reached the socket as messages of no known kind, and the error stopped every connection on the isolate
• A WebSocket whose 101 fails to go out ends, and so does a streamed response whose head fails to. Before, Dart went on writing to the freed exchange, which the next connection could be using
• A WebSocket upgrade drops the rest of a request body the handler left unread before the 101 goes out, up to 4 MiB with a Content-Length. A bigger body, or a chunked one that has not ended, closes the connection without the 101. Before, the rest of the body was read as frames, and the socket failed with 1002
• Dart's abort of a hijacked connection closes it at once. Before, an idle reactor got to it only at its next sweep, and never with every timeout off
• Each task commits 144 KiB of stack instead of zio's default 256 KiB. tls.zig is pinned to a fork whose handshake fits in it
• A cancel the sweeper takes back, for a wait that completed anyway, leaves nothing behind. Before, the connection's later timeouts read as cancels, and one could end the wait for the handler's answer
• An idle WebSocket or hijacked connection holds one task and its stack, where it held three
• A task that goes deeper than its committed 144 KiB grows its stack, whichever thread the isolate runs on. Before, the process crashed unless the isolate was on the thread that created its reactor
• An idle connection on Linux keeps reading after the Dart VM retires the thread its isolate ran on. Before, io_uring cancelled the read with that thread, and the connection hung or was reset

2.0.0-rc.5

• Client certificates: NativeTls.clientAuthorities names the CAs a client certificate must chain to, and the handshake requires one
• bind refuses a group join with other TLS settings than the group's
• ALPN: the handshake selects http/1.1 and refuses a client that offers only other protocols
• Encrypted private keys: NativeTls.password opens a PKCS#8 key under PBES2 with PBKDF2 and AES-128 or AES-256 CBC, or one behind OpenSSL's DEK-Info headers
• PKCS#1 RSA PRIVATE KEY files are read, the form cert-manager writes by default
• An IPv6 listener takes IPv4 clients on every platform, as in dart:io. Before, Windows and a Linux with net.ipv6.bindv6only=1 kept it IPv6 only
• zio pinned at upstream main (IOCP file streaming #857, task-group publish fix #877) with the fork's executor-tick patches on top
• Resolves with code_assets 1.1 and up, so a workspace on Flutter below 3.47, which pins meta to 1.18, can take the package
• A listening port on Windows refuses every other bind, as in dart:io. Before, a socket with SO_REUSEADDR could take it
• NativeAdapter.bind takes v6Only, as IOAdapter.bind does

2.0.0-rc.4

• Works on Windows: the acceptor and the reactors share one zio loop group, and the waiter thread waits on the completion port and owns the loop's wake
• Built with Zig 0.17.1

2.0.0-rc.3

• Initial release: NativeAdapter.bind, NativeExchange and serveNative on zio and std.http.Server. HTTP/1.0 and HTTP/1.1, keep-alive, several isolates on one server, prebuilt for Linux, macOS and Windows
• Streamed request and response bodies. maxInlineBody bounds the body read before the handler runs
• The prebuilt libraries use hardware AES for TLS. They need AES-NI, PCLMULQDQ and AVX on x64, and the ARMv8 crypto extensions on Linux and Windows arm64