Task: Consider compressing payload
This page documents a task in the Comms features story. It captures the goal, current status, acceptance, and any notes or results.
Goal
Evaluate adding payload compression to the comms layer and land an implementation if it pays off.
Status
| Field | Value |
|---|---|
| State | DONE |
| Parent story | Comms features |
| Now | Completed 2025-12-23. |
| Waiting on | None. |
| Next | None. |
| Last touched | 2025-12-23 |
Acceptance
- Benchmarks for representative messages (small CRUD, big result sets, history dumps).
- Decision recorded: which compressor (zstd by default), what size threshold triggers compression.
- Implementation lands behind a negotiated flag at session setup so both sides can opt in.
Plan
Captured during execution; cleared into the parent story on close.
Notes
Threshold matters: tiny messages get bigger when compressed. Negotiation keeps the protocol forward-compatible.
Result
Comms payloads are optionally compressed; benchmark numbers recorded in the comms knowledge doc.