- From: Harald Alvestrand <harald@alvestrand.no>
- Date: Wed, 8 Nov 2017 02:52:51 +0100
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 11/07/2017 01:00 PM, Silvia Pfeiffer wrote: > Just a thought: could we keep the RTCPeerConnection object around > rather than replace it with Javascript - it would be an aggregate > object that can be deconstructed through direct use of the other > objects. I think it would be useful, not just from a backwards > compatibility point of view, but also from a simplicity point of view > for the most basic use cases. My thought is that both RTCPeerConnection and RTCTransceiver would remain specified, and normally implemented as platform objects, so that anyone who wishes to continue to program against this model can do so. That's part of what the section titled "putting it all back together again" is about - as we add new capabilities to the platform, these should be accessible via RTCPeerConnection too. My worry is that none of us will have the resources needed to make that work, given how many years it's taken to get (for instance) Unified Plan implemented. > > Cheers, > Silvia. > > > On Tue, Nov 7, 2017 at 6:24 PM, Harald Alvestrand <harald@alvestrand.no> wrote: >> I've tried to put together my thinking about what I think we should try >> to achieve with WebRTC-NV. >> >> Chiefly, I've tried to look for the principles: What we should keep on >> doing, what we should make it possible to live without, and what we >> should extend further. >> >> I've enclosed it in PDF. It looked prettier that way. Comments can also >> be made here: >> >> https://docs.google.com/document/d/1pU4YR0hbH2IhE-s8_CggRdADps_9rambnfsOz3VH_ew/edit?usp=sharing >> >> Harald >> >> -- >> Surveillance is pervasive. Go Dark. >> -- Surveillance is pervasive. Go Dark.
Received on Wednesday, 8 November 2017 01:53:24 UTC