Application framing and bounded accumulation on TCP streams.
A worked byte-stream example, retained-input limits and the tests that expose incorrect framing.
Read the note : Framing messages on a byte streamThe full collection
Engineering notes
Networking, application boundaries, verification and delivery. Start with a subject that interests you.
All engineering notes
Connection-scoped certificate validation and identity management.
Connection-scoped TLS trust, identity bundles, certificate lifecycle and checks at the handshake boundary.
Read the note: Keeping TLS trust local to a connectionHTTP pipeline verification with controlled upstream services.
Choosing which behaviour belongs in a rule test, an application-host test or a packaged check.
Read the note : Testing at application boundariesApplication data direction, connection role and transport constraints.
TCP roles, transport restrictions and diode interface terminology, with a worked boundary diagram.
Read the note : Message direction and connection roleRouting, authentication and response contracts at the proxy boundary.
Where passthroughs, controller overrides and error handling meet.
Read the note : A proxy route is an application boundaryResolved endpoint validation for local loop prevention.
Prevent local feedback loops by checking resolved endpoints, wildcard listeners and reconnect destinations.
Read the note: Preventing feedback loops in configurable gatewaysInput policy, destination policy and release representation.
Separate input sanitisation, destination policy and release previews without confusing them with validation or authorisation.
Read the note: Sanitisation belongs to a boundaryTechnical note
Preserving message semantics during transformation
Message processing / Serialisation
Typed XML models, ordered geometry and round-trip verification.
Preserve modelled XML attributes and vertex order while applying explicit field policy, with an independently tested example.
Read the note: Preserving message semantics during transformationCache validity, per-upstream coordination and renewal failure handling.
Coordinate concurrent credential cache misses and define expiry, cancellation and recovery behaviour at the authentication boundary.
Read the note: Coordinating credential renewal under concurrencyApplication-owned contracts and explicit dependency direction.
Keep application rules independent of transport and concrete integrations, with explicit ownership and dependency direction.
Read the note : Making dependency boundaries explicitA proposed bounded diagnostic collector for recovery support.
A proposed bounded, read-only diagnostic collector with timeouts and deliberate handling of sensitive output.
Read the note : Recovery evidence collection