Documentation
¶
Overview ¶
Command memsrv is the server under test for the G2 idle-connection memory baseline (RFC-0001 §6.1/§6.2, equivalence-spec §3.6).
It is deliberately the smallest complete live application: one fragment, one event, one int64 of state. RFC-0001 §6.2's composition budget is a LIBRARY-per-connection budget whose application-state line is 500 B ("the counter example's is 24 B"), and a measured figure that is meant to correct that table must not carry an application the table never budgeted for.
TLS ¶
This binary constructs exactly one listener and it is plaintext. There is no -tls flag, no certificate path, and no crypto/tls import — equivalence-spec §3.6's boundary rule ("the measured container serves plaintext HTTP/WebSocket on its container port") is enforced here by there being nothing to misconfigure, and /introspect reports tls_listeners so the harness can assert it from outside rather than trust this comment. In-process TLS is a separate, labelled secondary in §3.6 and is NOT what this binary is for.
Observability ¶
-observability=on wires a real OpenTelemetry meter and tracer provider and a slog JSON logger, which is what equivalence-spec §5.6 calls the headline configuration ("that is what a user gets") and what puts the provenance log inside the measured number. -observability=off leaves all three nil, which is the configuration RFC §6.2's table describes. Both are measured; the manifest records which.
Usage:
memsrv -addr :8080 -origin http://127.0.0.1:18080 -observability on
Source Files