pure/link/tls.h, branch masterVerified execution runtime unifying state, persistence, and replication.
http://git.yeowoo.org/pure/atom?h=master2026-10-01T08:10:55ZDeliver wires on the sending loop, a step at a time (017, 2b-2)2026-10-01T08:10:55Zeunhhunecpition205@gmail.com2026-10-01T08:10:55Zurn:sha1:5f5603ce239dce08ae2ec4b0fa828787b220493c
A wire is now a sender of link/sending.h: its request goes on a
non-blocking socket as far as the socket takes it (connect, TLS
handshake, write, answer read), and its round waits for the socket or
its deadline (10 s with nothing moved). The answer is read as it comes:
the head whole, then a sized body counted down, a chunked one (few and
small) parsed again as it grows, or a body to the close. The crypto
table (version 6) takes the TLS handshake a step at a time, and reads
and writes say what they wait for. The owner pushes a wire once a turn,
as it does a link. A host whose app sends to ten links and ten wires
has 5 threads where it had 24 (none: 3).
Put the links and the crypto they use in link/, a part of their own2026-09-29T06:06:27Zeunhhunecpition205@gmail.com2026-09-29T06:06:27Zurn:sha1:a052b95c8135cdc5f9b91f8efc991cac80fbbe8b
libpure-link.a holds them; pure-serve and the M5 harness link it instead
of naming its source files.