diff options
| author | eunhhu <[email protected]> | 2026-09-28 17:37:41 +0100 |
|---|---|---|
| committer | eunhhu <[email protected]> | 2026-09-28 17:37:41 +0100 |
| commit | 745efcd4f19b59bcfb131df2d127a3387a544e84 (patch) | |
| tree | 3e001fdd0a695f9a9aaf567e07ad00415f3cf330 /serve/test-message-json.c | |
| parent | 502f70dbd66debcf1cb0328427831ec14926504b (diff) | |
| download | pure-745efcd4f19b59bcfb131df2d127a3387a544e84.tar.gz pure-745efcd4f19b59bcfb131df2d127a3387a544e84.zip | |
Link two nodes without a connection over UDP (093, design 011's first stage)
pure-serve --send OUTPUT=pure://host:port/INPUT sends an output's saved
sends to another node's --link-port with no handshake: the first packet
carries records. Keys come from the two nodes' keys (X25519, HKDF-SHA256,
AES-128-GCM), with a random run in each packet's header so no nonce
repeats across restarts; nothing is stored for them. What lasts is the
apps' own: the sender's outbox and the receiver's heard numbers
(pure_app_heard, new). The sender detects losses as RFC 9002 says, with
NewReno, and trims a send once the receiver says it stored it; the
receiver hands the owner whole records in order, which it applies from
the one after the source's last heard number, stopping at a gap, and
answers how far it stored with every acknowledgment. Stored bytes are
the bytes on the wire: an output and an input of one shape need no JSON.
server_links_udp kills the receiver, the sender, then both (-9) while
four clients buy: every saved order is applied once, with no handshake
(five runs, 10k-11k orders each). server_links_udp_lossy does it again in
a namespace of its own with the link's packets delayed, lost (3 %) and
reordered (10 %) by netem (three runs, 11k-12k orders).
Diffstat (limited to 'serve/test-message-json.c')
0 files changed, 0 insertions, 0 deletions
