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

Re: [SPAM] Re: What is missing for building "real" services?

From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Date: Thu, 16 Jan 2014 10:05:35 +1100
Message-ID: <CAHp8n2=bS1m=5WgaGBsKKs9LK3sf1xvjJqpTJ0m4U3yhqM7heQ@mail.gmail.com>
To: Justin Uberti <juberti@google.com>
Cc: Tim Panton new <thp@westhawk.co.uk>, Jan-Ivar Bruaroey <jib@mozilla.com>, public-webrtc <public-webrtc@w3.org>, Alexandre Gouaillard <agouaillard@gmail.com>, Randell Jesup <randell-ietf@jesup.org>
On Thu, Jan 16, 2014 at 9:34 AM, Justin Uberti <juberti@google.com> wrote:
> Blocking HTTPS makes it impossible to share a Google Docs doc or
> presentation
>
> Look, this is a hard problem, and we've come to a point where use of the
> screensharing feature in Chrome requires jumping through a hoop (i.e.
> installing an extension), but not a ridiculously difficult one. I suspect
> that web applications will find fairly elegant ways to incorporate this into
> their flow.

It's not just the Chrome extension that you need - you will need one
for every browser. Also, what do you do on mobile devices? There is
nothing elegant about installing browser extensions.

WebRTC brings the promise to not have to deal with extensions and
screensharing is a core feature of video conferencing applications. It
just makes no sense to me to ignore this requirement for WebRTC and
push it into a browser extension. It's a step back in technology. I
think we need to think harder about how to solve this problem in a way
that makes it part of the Web platform. I think we've given up too
quickly.

Silvia.
Received on Wednesday, 15 January 2014 23:06:22 UTC

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