- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Jun 2021 16:11:03 +0000
- To: public-webrtc-logs@w3.org
> On a technical level, it should be straightforward in case of `SCTP_SEND_FAILED_EVENT` to return the failed message in the onerror event of a data channel. It doesn't really fit the definition of the error event though. Also, it only triggers on the receiver side and messages that have never been sent will not even trigger this, so it's completely arbitrary and doesn't tell you much. You do need the event though to clear the receive buffers when running in message interleave mode. > In case of a `SCTP_PARTIAL_DELIVERY_EVENT`, wouldn't you also receive `SCTP_SEND_FAILED_EVENT` too? Like I said, I'm not sure if abandoning a message that was marked as "allowed to be unreliable" even triggers this event. If it does, then probably yes. -- GitHub Notification of comment by lgrahl Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/50#issuecomment-863372272 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 June 2021 16:11:39 UTC