{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/webrtc-pc/issues/230","labels_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/230/labels{/name}","comments_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/230/comments","events_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/230/events","html_url":"https://github.com/w3c/webrtc-pc/issues/230","id":80571490,"number":230,"title":"Add support for WebRTC Data Channel in Workers","user":{"login":"feross","id":121766,"avatar_url":"https://avatars.githubusercontent.com/u/121766?v=3","gravatar_id":"","url":"https://api.github.com/users/feross","html_url":"https://github.com/feross","followers_url":"https://api.github.com/users/feross/followers","following_url":"https://api.github.com/users/feross/following{/other_user}","gists_url":"https://api.github.com/users/feross/gists{/gist_id}","starred_url":"https://api.github.com/users/feross/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/feross/subscriptions","organizations_url":"https://api.github.com/users/feross/orgs","repos_url":"https://api.github.com/users/feross/repos","events_url":"https://api.github.com/users/feross/events{/privacy}","received_events_url":"https://api.github.com/users/feross/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/w3c/webrtc-pc/labels/LATER","name":"LATER","color":"ededed"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":14,"created_at":"2015-05-25T15:31:20Z","updated_at":"2016-01-08T12:42:42Z","closed_at":null,"body":"#### Proposal\r\n\r\nSupport WebRTC Data Channel in Workers (`WebWorker`, `ServiceWorker`, etc.)\r\n\r\nWebRTC 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.\r\n\r\n#### Use Cases\r\n\r\nDataChannel 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.\r\n\r\nDataChannel in a `WebWorker` would support offloading CPU intensive data transfer/processing to another thread.\r\n\r\n#### What about security?\r\n\r\nUsing WebRTC data channels in a worker is no different from a security/privacy perspective than using  WebSocket. There's no user permission prompt to open a WebRTC data channel."},"comment":{"url":"https://api.github.com/repos/w3c/webrtc-pc/issues/comments/169988229","html_url":"https://github.com/w3c/webrtc-pc/issues/230#issuecomment-169988229","issue_url":"https://api.github.com/repos/w3c/webrtc-pc/issues/230","id":169988229,"user":{"login":"stefhak","id":1180334,"avatar_url":"https://avatars.githubusercontent.com/u/1180334?v=3","gravatar_id":"","url":"https://api.github.com/users/stefhak","html_url":"https://github.com/stefhak","followers_url":"https://api.github.com/users/stefhak/followers","following_url":"https://api.github.com/users/stefhak/following{/other_user}","gists_url":"https://api.github.com/users/stefhak/gists{/gist_id}","starred_url":"https://api.github.com/users/stefhak/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stefhak/subscriptions","organizations_url":"https://api.github.com/users/stefhak/orgs","repos_url":"https://api.github.com/users/stefhak/repos","events_url":"https://api.github.com/users/stefhak/events{/privacy}","received_events_url":"https://api.github.com/users/stefhak/received_events","type":"User","site_admin":false},"created_at":"2016-01-08T12:42:42Z","updated_at":"2016-01-08T12:42:42Z","body":"This was discussed at the WebRTC WG meeting during TPAC, and it was decided to add this functionality pending a security review. That security review has been done, and there are active PRs ( #317 and #445 ). However, more work is needed on those PRs."}}