W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2013

Re: Discussing new API proposals

From: Peter Thatcher <pthatcher@google.com>
Date: Wed, 17 Jul 2013 18:38:16 -0700
Message-ID: <CAJrXDUFT0iiN1HEWxbnJAFB6tJ7dRzQCpKOwoU4_ppfnZTsWJg@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: piranna@gmail.com, Stefan HÃ¥kansson LK <stefan.lk.hakansson@ericsson.com>, cowwoc <cowwoc@bbs.darktech.org>, public-webrtc <public-webrtc@w3.org>
Chrome hasn't finished implementing SCTP-based data channels.  I'll take
the blame for that.  It's simply taken longer than I thought.  I know it
may be a broken record at this point, but it should be done Real Soon Now

And once its done, I assume it will better than useless.
On Jul 17, 2013 3:11 PM, "Eric Rescorla" <ekr@rtfm.com> wrote:

> On Thu, Jul 18, 2013 at 1:46 AM, piranna@gmail.com <piranna@gmail.com>wrote:
>> I agree, it was supossed to have operative DataChannels last December,
>> and the fact is that 7 months ago the proposed date they are fairly useless
>> and real-world usage of WebRTC are mainly proof of concept... I have ear
>> people saying WebRTC is a hype and others that's a technology could get to
>> be desacredited due to release it too early as it's hapenning now, only
>> don't now if just by an unlucky accident or it's being done this way in
>> purposse (too much decentrliced power on the browsers out of control of the
>> traditional owners...).
> I'd like to focus on this point. In what way are data channels  as
> currently specified
> "fairly useless"?
> -Ekr
Received on Thursday, 18 July 2013 01:38:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:49 UTC