Data Channel Backpressure and Peer State

Working case

During a consultation, reviewer 29 points to region 47 of a scan and sends an annotation hint. Reviewer 47 sees it immediately, but the actual case note is saved through the case API with an expected revision. When the peer channel pauses, reviewer 29 can continue editing locally; the client stops sending hints once buffered bytes cross its limit. When the channel returns, it may send the latest cursor position rather than replaying every obsolete movement. The saved note remains available even if the peer never reconnects.

Implementation boundary

function maySendHint(channelState, bufferedBytes, maximumBytes) {
  return channelState === "open" && bufferedBytes < maximumBytes;
}
console.log(maySendHint("open", 48000, 47000));
// Output: false

Choose the channel reliability and ordering settings to match each message class. Keep payloads small, validate schema and maximum size at both endpoints, and never infer authorization from a live peer connection. Gate send on open state and a bounded bufferedAmount threshold; resume after bufferedamountlow or a fresh state check. Coalesce replaceable events such as pointer movement. For durable actions, call a server endpoint that checks current room and object permissions, revision, and idempotency key. On leave, close the data channel, connection, and media tracks.

Cost and boundaries

Per-message overhead can exceed useful data if every pointer pixel becomes an event. Coalescing reduces network and render work from O(movements) toward O(display frames) for ephemeral state. Reliable ordered delivery can let one large message delay later ones, while weaker delivery can drop hints; neither is a replacement for persistence. Track queue depth, dropped or coalesced hints, end-to-end hint delay, server-save conflict rate, and channel closure. Avoid putting raw private documents in this transport merely because it is encrypted.

Failure trace

A drag gesture emits thousands of messages while the network slows, and bufferedAmount grows until the tab runs out of memory. Add a threshold and coalesce hints. Another implementation treats a received peer message as a committed case note; when the remote tab closes, the note vanishes from history. Test closed and closing channel states, malformed payload, a large message, slow network, peer reconnect, stale case rights, duplicate server save, and a conflict between two editors.

Verification

• Buffered data has a hard application limit.
• Durable notes survive peer teardown through the case API.
• Live channel state never grants case permission.

Practice drill

Send 62 pointer updates under a throttled link and enforce a 47-kilobyte queue cap. Verify the latest visible position wins while old positions may be discarded. Save a note through the server, close the peer connection, and reload the case: the note must still exist. Revoke reviewer 47 and attempt a new durable write from that browser; the server must reject it even if an old data channel remains open.

Decision note

Use the peer channel for bounded ephemeral interaction and the authorized server contract for durable state.

Common Mistakes

• Sending every pointer movement without coalescing.
• Assuming send means remote persistence.
• Ignoring a closed channel when queueing messages.

Connected lessons

Build Project: private peer consultation and review Web Development: browser compute and peer sessions quiz; follow WebRTC and Peer Media Sessions; Media Capture Consent and Track Lifecycle; WebRTC Signaling, Room Authorization, and Offer Order; WebRTC ICE, TURN Fallback, and Session Recovery; Idempotent Write Requests and Lost Responses; Server-Sent Events or WebSocket for Live Views.