- From: Tim Panton via GitHub <noreply@w3.org>
- Date: Tue, 19 May 2026 09:31:19 +0000
- To: public-webrtc-logs@w3.org
I'm in favour of adding this info - but I wonder if it wouldn't be better to expose the actual SCTP names rather that an approximate description of what they do. - For example messageInterleavingEnabled might give a misleading impression of the limitations of the actual implementation. Giving the SCTP name forces the developer to look them up and (hopefully) understand what they can and can't do and how they may interact with each other. Also these capabilities are static (per association). Is there a way to separate them from the more dynamic properties like unAckedData ? - Are they actually properties of the SCTPTransport rather than stats ? -- GitHub Notification of comment by steely-glint Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/821#issuecomment-4486383593 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 May 2026 09:31:19 UTC