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

Re: WebRTC Data Channel in Workers Proposal

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Tue, 26 May 2015 16:26:32 +0000
To: Feross Aboukhadijeh <feross@feross.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1D23EC53@ESESSMB209.ericsson.se>
On 26/05/15 17:11, Feross Aboukhadijeh wrote:
> I would like to propose that we support WebRTC Data Channel in
> Workers (`WebWorker`, `ServiceWorker`, etc.)

Thanks for the proposal!

> WebRTC DataChannel is basically a drop-in replacement for
> `WebSocket`, except it's peer-to-peer. For all the same reasons that
> `WebSocket` was added to the `Worker` spec, we should add WebRTC
> DataChannel.

The WebRTC data channel is attached to a RTCPeerConnection, I assume the 
natural thing to do would be to make the RTCPeerConnection also usable 
in Workers?
> Here are some possible use cases:
> - DataChannel in a `ServiceWorker` would support the use case of
> "peer assisted delivery" a la
> [PeerCDN](https://www.peercdn.com/faq.html), CDN/P2P CDN video
> streaming delivery, file transfer, etc.
> - DataChannel in a `WebWorker` would support offloading CPU intensive
> data transfer and subsequent processing to another thread.
> - DataChannel in a `SharedWorker` would let one construct and reuse a
> DHT (a decentralized/distributed lookup service similar to a hash
> table) across tabs. Useful for routing to nodes in decentralized
> applications.
> Websockets are already available in Workers, so there likely aren't
> any new security/privacy issues, just potential for exciting new data
> channel use cases!

Received on Tuesday, 26 May 2015 16:27:00 UTC

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