- From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
- Date: Thu, 06 Jul 2017 14:54:21 +0000
- To: public-webrtc-logs@w3.org
My assumption was that the `maxMessageSize` attribute would return the intersection of the remote endpoint's capabilities and the browser's supported max message size. So if the remote endpoint says "max-message-size=0", but the implementation does have a limit, the attribute would return that limit. So maybe we just need to make that more clear? And future-proof ourselves by handling the max size of 0 where we currently say: > If the size of _data_ exceeds the value of `maxMessageSize` on _channel_'s associated `RTCSctpTransport`, throw a `TypeError`. -- GitHub Notification of comment by taylor-b Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1446#issuecomment-313420565 using your GitHub account
Received on Thursday, 6 July 2017 14:54:27 UTC