- From: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Jan 2019 11:41:05 +0000
- To: public-webrtc-logs@w3.org
How this API would be applicable to unreliable DC? My wild guess is that either when the SCTP transports reach the `maxPacketLifeTime` or `maxRetransmits` limits, an exception on the sender will be raised in the writable stream ready/send, and also on the receiver read stream when the abandon SACK is received? Would it be possible to abort\abandon an ongoing message? Also, I assume that write/recv chunks boundaries are not preservesd(which is fine), right? -- GitHub Notification of comment by murillo128 Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1732#issuecomment-458098650 using your GitHub account
Received on Monday, 28 January 2019 11:41:07 UTC