W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2014

Re: RTCDataChannel characteristics and failures

From: <piranna@gmail.com>
Date: Thu, 2 Jan 2014 13:36:41 +0100
Message-ID: <CAKfGGh0oW2NL_=CSFM2iruEdV_HvQyFUpYYnCgxOEqQsZhA98A@mail.gmail.com>
To: Harald Alvestrand <harald@alvestrand.no>
Cc: public-webrtc <public-webrtc@w3.org>
For example, highly coupled realtime tasks like P2P video distribution. You
would be interested in have a timeout to don't send info out of time, but
also have a max number of retransmits to don't waste bandwidth and try
another source.

Send from my Samsung Galaxy Note II
El 02/01/2014 09:36, "Harald Alvestrand" <harald@alvestrand.no> escribió:

> On 12/30/2013 12:09 AM, piranna@gmail.com wrote:
>
>>
>> > > for some use cases...
>> > Any concrete example?
>> >
>> Application-based fine-grain control of the transmissions.
>>
>>  When asked for a concrete example, please give a concrete example of an
> application that needs it.
>
> It's always possible to send in unreliable mode and implement your own
> mechanisms for reliability; any extension to the spec needs to be backed
> with an use case that makes it clear why it's worth changing.
>
>
>
Received on Thursday, 2 January 2014 12:37:09 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:37 UTC