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

Re: What is missing for building "real" services?

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Mon, 23 Dec 2013 20:08:25 +1100
Message-ID: <CAHp8n2mQC_HFafyz8FCYVDRXADtpGsCtNXuEHaRo4QyT+xYsAw@mail.gmail.com>
To: Emil Ivov <emcho@jitsi.org>
Cc: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>, public-webrtc <public-webrtc@w3.org>
Mostly it's the implementations, not the specs per se, but of course
specs have to continue evolving as the implementations get better and
more complete and find corner cases.


On Sun, Dec 22, 2013 at 9:41 PM, Emil Ivov <emcho@jitsi.org> wrote:
> * stable multi-stream support (this is mostly for firefox and the android
> version of Chrome)
> * support in IE, iOS and Safari
> are the main issues that we've been seeing as adoption blockers.
> --sent from my mobile
> On 22 Dec 2013 08:52, "Stefan Håkansson LK"
> <stefan.lk.hakansson@ericsson.com> wrote:
>> During the telechat last Thursday some persons said that WebRTC is
>> sufficient to do demos, but not sufficient for building a "real" service
>> on top of.
>> I would really like to know more. If you can't build a service on top
>> off WebRTC I think we have failed. Would anyone care to expand a bit on
>> what is missing/wrongly designed? And explain the context/use-case.
>> Stefan (speaking for himself only)
Received on Monday, 23 December 2013 09:09:14 UTC

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