Re: [rtcweb] Open data channel issues

On 04 Mar 2014, at 07:30, Randell Jesup <randell-ietf@jesup.org> wrote:

> On 3/4/2014 2:00 AM, Martin Thomson wrote:
>> On 4 March 2014 03:38, Randell Jesup <randell-ietf@jesup.org> wrote:
>>> To take your suggestion:
>>> a) applications assume 16KB if ndata wasn't negotiated (per the current
>>> suggestion)
>>> b) implement ndata and EOR support in the browsers, and drop the 16KB limit
>>> when ndata is negotiated.
>>> All this needs is "is ndata supported by this association" exposed to the
>>> app; no sdp changes needed.  (One less dependency!)
>> 
>> Or, to avoid vestigal crap in the API in the end state, when you
>> install the 16K limitation, add an indicator that applications can
>> check.  Once you remove the cap, remove the indicator.
>> 
>> if (dataChannel.isNotVeryGood) {
>>   chunkMessage(message);
>> } else {
>>   dataChannel.send(message);
>> }
> 
> Yup, that works for me.  dataChannel.requiresFragmentation would be the wordy version or mustFragmentAt16K for self-documentation.
Or you return a number which gives you the limit if you don't want to specify the
16K limit...

Best regards
Michael
> 
> -- 
> Randell Jesup -- rjesup a t mozilla d o t com
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> 