Re: [rtcweb] Open data channel issues

[Randell Jesup <[e-mail]>]

On 3/3/2014 8:28 AM, Justin Uberti wrote:
> On Mon, Mar 3, 2014 at 3:44 AM, Randell Jesup <[e-mail] 
> <mailto:[e-mail]>> wrote:
>
>     On 3/3/2014 6:18 AM, Justin Uberti wrote:
>>     On Sun, Mar 2, 2014 at 6:42 PM, Randell Jesup
>>     <[e-mail] <mailto:[e-mail]>> wrote:
>>>
>>>     So I still think manual chunking seems like a reasonable thing
>>>     to support. I don't quite get the congestion control concerns;
>>>     just because there is a max chunk size doesn't mean the impl
>>>     can't buffer multiple chunks in bufferedAmount; the app could
>>>     let that fill up to a degree to avoid having to poll constantly
>>>     to prevent underrun.
>>
>>         On a slow link this will work if the browser isn't janky.  On
>>         a fast link GC pauses and other things may cause the buffer
>>         to drain out and go idle for significant periods.
>>
>>
>>     Since the amount buffered is up to the app, the app can just
>>     increase the buffer size to provide enough data to cover the next
>>     second or so of transfer.
>
>     How does the app increase the size of the internal SCTP buffers? 
>     (And that buffer is shared by all channels, of course).
>
>
> What I meant is the app can make multiple calls to send() at a time, 
> each with a chunk, which will be buffered in the api layer and 
> increase bufferedAmount.

Aha - that explains "increase the buffer size".  Yes, that will work, 
modulo that the app will have to track the actual bandwidth by either 
monitoring how fast the bufferedAmount drains, or via a JS API to report 
bandwidth ala the bug I opened on JS interaction with congestion 
control.  I still feel this pushes some level of congestion control into 
the JS app (and done like trying to thread needles with oven mitts on - 
ok, mild exaggeration) or the app will simply ignore this issue (likely) 
and get sub-optimal performance, perhaps significantly.  So I think more 
thought would be useful here, especially at the W3/JS level.

If we have the bandwidth reporting, having the app choose a reasonable 
amount of buffering would be much easier/simpler.

-- 
Randell Jesup -- rjesup a t mozilla d o t com