Re: [webrtc-extensions] Consider an API for non-delivered messages in SCTP datachannels (#50)

I'm unsure whether abandoning a message even triggers `SCTP_SEND_FAILED_EVENT` on the sender side. Would have to dig in the spec what's the case here, but maybe @tuexen knows it without looking. Even if it does, I don't see value in it unless all unsent messages can be reliably recovered from it **immediately** when ICE goes into failed. That would make it somewhat interesting (especially for reliable channels).
Note that there's also `SCTP_PARTIAL_DELIVERY_EVENT` which indicates that some parts of a message have been received but it's being abandoned.

But I'm not convinced this is worth the effort. If an application really wants to make sure it doesn't lose messages (reliable) or needs to know which messages have been abandoned (unreliable), it's fairly easy and safer (talk browser bugs here) to count and ack by itself.

-- 
GitHub Notification of comment by lgrahl
Please view or discuss this issue at https://github.com/w3c/webrtc-extensions/issues/50#issuecomment-863340900 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 15:32:54 UTC