W3C home > Mailing lists > Public > public-webrtc@w3.org > May 2018

Raw data API - 5 - misc notes

From: Harald Alvestrand <harald@alvestrand.no>
Date: Tue, 29 May 2018 08:32:40 +0200
To: "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <08726e4d-7849-f02a-0682-28384732bbc3@alvestrand.no>
**


    *Relationship to workers and processes*

*

Note - not part of this proposal, but part of context:


Processing of real-time data needs to be performed real-time. Living on
the browser main thread makes this impossible, and even living inside
the renderer task makes it hard.

We have to define means of exchanging MediaStreamTracks, RTPSenders and
RTPReceivers between processes as part of making this type of thing
performant.


    Layering of API

Attaching these access calls to the MediaStreamTrack is just one option.

Other options:

  *

    Let them be separate objects: sources (like canvas, <video>,
    RTPReceiver) or sinks (like RTPSender, MediaRecorder or <video>

  *

    Let them be an object vended from the MediaStreamTrack


An advantage (?) with separate objects is that they can be made
transferable without making streams or tracks transferable.

*

-- 
Surveillance is pervasive. Go Dark.
Received on Tuesday, 29 May 2018 06:33:07 UTC

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