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

Re: WebRTC in {Web,Shared,Service} Workers

From: westhawk <thp@westhawk.co.uk>
Date: Mon, 9 Apr 2018 11:32:38 +0200
Cc: public-webrtc@w3.org
Message-Id: <493D7565-E3EB-4673-B18F-69FE7A2E7F62@westhawk.co.uk>
To: Isaac Kwan <i@isaac.pw>
This is an important topic - I’d love to have any access to RTCDataChannel in workers - especially service workers….

I believe the current thinking is that defining a safe/relevant/complete subset of RTCPeerConnection
to allow RTCDataChannel’s to be set up in a worker is a _lot_ of work (especially thinking through the 
security requirements around valid SDP/identity). So the discussion centered on a proposal that seems
(on the surface) simpler. That is allowing  live RTCDataChannels to be transferred to workers 
with postMessage() in the same way that MessagePorts can. 


> On 8 Apr 2018, at 18:13, Isaac Kwan <i@isaac.pw> wrote:
> I am aware that there has been discussions in the mailing list and
> GitHub on this, and that I probably are over-simplifying it, but is
> there a reason why we can't expose RTCDataChannel etc to workers?
> This does not involve transferring ownership of existing connection
> from other scopes, connections are set up in the worker and ends
> "automatically" when it goes out of scope (e.g. exceeds the service
> worker timeout limit).
> Thanks
Received on Monday, 9 April 2018 09:33:26 UTC

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