- From: Lennart Grahl via GitHub <sysbot+gh@w3.org>
- Date: Fri, 30 Jun 2017 22:49:26 +0000
- To: public-webrtc-logs@w3.org
lgrahl has just created a new issue for https://github.com/w3c/webrtc-pc: == RTCSctpTransport.maxMessageSize 0 case == This spec's `RTCSctpTransport.maxMessageSize` description says: > The maximum size of data that can be passed to RTCDataChannel's send() method. In [the related SDP spec](https://tools.ietf.org/html/draft-ietf-mmusic-sctp-sdp-26#page-8), it's specified that > If the SDP 'max-message-size' attribute contains a maximum message size value of zero, it indicates the SCTP endpoint will handle messages of any size, subject to memory capacity etc. So, there is a `maxMessageSize = 0` case we need to handle in some way. While messages of arbitrary size may not be possible in the browser as this specification does not provide a way to deliver partial messages (e.g. for this spec, all messages need to be buffered until they are complete), other implementations may support this (one already does). This has been discussed in https://github.com/w3c/ortc/issues/626 as well. Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1446 using your GitHub account
Received on Friday, 30 June 2017 22:49:32 UTC