Protocol evidence · August 4, 2026
WebSocket framing, case by case.
Autobahn exercised the same public server API through both task lanes and through the OpenSSL-backed WSS transport. Separate runs cover configurable boundaries, RFC 7692 compression, and echo timings by lane and transport. Historical per-run checkout revisions were not captured; the labels below distinguish the implementation bytes from the first complete 14-profile harness and report.
01 / RESULT
No core framing failures in either lane or over TLS.
02 / PROFILES
Four test families.
Choose a lane and transport within each family. Every variation retains its individual verdicts and normalized JSON.
RFC 6455
Core framing
Framing, fragmentation, control frames, close handling, masking, lengths, and UTF-8 behavior.
Sections 9.1–9.6
Message limits
Text, binary, fragmentation, and chopped delivery from 64 KiB through the configured 16 MiB maximum.
RFC 7692 · Sections 12–13
Compression
permessage-deflate negotiation and compressed messages across both task lanes and transports.
Sections 9.7–9.8
Timing observations
Release/-O3 loopback echo observations across six text and binary payload sizes.
03 / COMPRESSION
864 compressed-message and negotiation cases.
Flyology explicitly opts into permessage-deflate with no context takeover in either direction. The pure-Ada decoder accepts stored, fixed-Huffman, and dynamic-Huffman DEFLATE blocks while enforcing the configured decompressed message limit.
04 / TIMING
48,000 sequential echoes across lanes and transports.
All 48 section 9.7–9.8 timing probes passed. Every lane and transport variation completed 1,000 sequential round trips at each text and binary payload size from a recorded Alire release build with -O3.
These loopback observations include case setup and close work. They are recorded for regression comparison, not as a portable throughput or latency claim.
05 / BOUNDARY
The limit is application policy.
All 42 boundary and chunking cases pass from 64 KiB through 16 MiB. The adapter explicitly selects the 16 MiB supported maximum; ordinary calls retain Flyology's 1 MiB default.
Core framing, compression, and timing were repeated over wss:// in both lanes. The message-limit campaign used loopback ws://.