Open Bug 2083166 Opened 1 month ago Updated 2 days ago

WebTransport datagrams: apply backpressure instead of dropping oldest incoming datagram / ignoring outgoing limit

Categories

(Core :: Networking, enhancement, P2)

enhancement

Tracking

()

People

(Reporter: jesup, Unassigned)

References

Details

(Whiteboard: [necko-triaged])

Review feedback on D334395 (Bug 2023587) asked for a bug to fix datagram backpressure.

Incoming: WebTransportDatagramDuplexStream::NewDatagramReceived drops the oldest
queued datagram once incomingMaxBufferedDatagrams is reached. Revisit whether
and how backpressure should be exerted on the transport (e.g. withholding
flow-control credit/reading from neqo) rather than dropping in the content
process.

Outgoing: outgoingMaxBufferedDatagrams only decides whether write()'s promise
resolves immediately; it does not bound the outgoing queue.

Severity: -- → S3
Priority: -- → P2
Whiteboard: [necko-triaged]
See Also: → 2095447
You need to log in before you can comment on or make changes to this bug.