W3C home > Mailing lists > Public > public-webrtc@w3.org > June 2012

Re: Keeping up data channel

From: Harald Alvestrand <harald@alvestrand.no>
Date: Wed, 13 Jun 2012 09:07:13 +0200
Message-ID: <4FD83C21.4080701@alvestrand.no>
To: public-webrtc@w3.org
On 06/13/2012 01:01 AM, Martin Thomson wrote:
> On 12 June 2012 13:15, Stefan Hakansson LK
> <stefan.lk.hakansson@ericsson.com>  wrote:
>> I think we need to make developers close the PeerConnection when it is not
>> needed. A way to promote this would of course be to make PeerConnection set
>> up fast.
> Unfortunately, responsiveness is also a trait that is valued highly.
> Setup for data channels is currently prohibitively long.  Applications
> that are not specifically targeting mobile users will have abysmal
> performance on mobile networks initially.  Expect the radio to remain
> on constantly.
I'm really looking forward to having an implementation up so that I can 
test what the setup time is for various media path RTTs and signalling 
path RTTs.

How far down do you think we have to drive the setup time before you 
would not call it "abysmal"?

(for reference: the responder's time from hitting "allow" in Chromium to 
having a video on the screen with apprtc.appspot.com is subjectively 
quite short - below 2 seconds - I can't measure it more accurately 
without generating logs for it.)
> I expect that many developers will come down on the wrong side of the
> tradeoff, especially since we give them such an awful set of choices -
> massive latency or massive battery use.  Natural selection of a sort
> will prevail.  I suspect that problems will surface pretty quickly.
> Mobile applications that are bad at this tend to get a reputation
> pretty quickly and people stop using them.
> --Martin
Received on Wednesday, 13 June 2012 07:07:41 UTC

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