-
Notifications
You must be signed in to change notification settings - Fork 42
Description
We have combined the half-closed-remote and half-closed-local states from the QUIC transport document into a single "closing" state. Also, we have both finish and reset methods. Some questions:
-
Does receipt of a STREAM frame with the FIN bit set automatically cause the RTCQuicStream object to send a STREAM frame with the FIN bit set in reply? Or does this not happen until the local peer calls finish()?
-
Does receipt of a STREAM frame with the FIN bit set affect either the Readable or Writeable slots on the local peer?
-
Does receipt of a RST_STREAM frame automatically cause the RTCQuicStream object to send a RST_STREAM frame in reply?
-
Does receipt of a RST_STREAM frame cause both the Readable and Writeable slots on the local peer to be set to false?
-
Calling reset() causes both the Readable and Writeable slots to transition to false, correct?
-
Calling finish() causes the Writeable slot to transition to false, but does not affect the Readable slot on the local peer, correct?