typed event -> validated + authorized -> one transaction (task + job) -> worker lease -> completion transaction + outbox -> dispatcher -> revisioned patch
Two connections, and the rows keep them apart: the page and its assets arrive on the
document's own connection, while the live session is a WebTransport session over HTTP/3 that shares
nothing with it. The first row is read from the browser's own connection record; the session rows are
echoed by the server from the request it actually received, so neither side is taken on trust.
Reproduce it
without a browser: python3 scripts/webtransport_interop.py zix.entwurfswerk.dev 443 /tasks
walks the QUIC and TLS handshakes, sends the extended CONNECT, and reports the status this server
answered. Its echo checks are written for the echo example, so against this page they are expected to
report a mismatch.
One run is one batch of 100 round trips per channel. Each percentile names the batch it describes, not the whole history, and batches vary. A round trip here is an application round trip: it includes the network path and the work both ends do.
| id | title | state | attempts | result |
|---|