Purpose

Ensure the Transform channel behaves as best-effort / latency-bounded (only the newest state matters), so low-bandwidth or overloaded links don’t accumulate stale Transform messages that “play back” minutes later. This also helps protect control traffic (RPC / Network Variables / heartbeat) from being indirectly impacted by Transform backlog.

Overview

• Receiver-side coalescing: On the Transform SUB receive loop, drain all pending frames and deserialize only the last message each tick/frame.
• Queue bound: Set RCVHWM on the Transform SUB to a small value so the socket can’t buffer large amounts of stale Transform traffic.
• Drop visibility: Add lightweight metrics/logging (e.g., dropped/drained count, max backlog observed) to verify the system is discarding stale frames as intended.
• Validation scenario: Reproduce with the throttled-link + 100-client simulator test and confirm no prolonged delayed updates continue after the simulator stops (Transform traffic should stop quickly, not “leak out” for minutes).