Make RTCDataChannels transferable (to workers)

NEW
Unassigned

Status

()

P3
normal
Rank:
23
3 years ago
11 months ago

People

(Reporter: jesup, Unassigned)

Tracking

({dev-doc-needed})

Trunk
dev-doc-needed
Points:
---

Firefox Tracking Flags

(firefox44 affected)

Details

(Reporter)

Description

3 years ago
From my posting to the W3 public-webrtc list.  The PR is 317

Use-case:
A number of applications using RTCDataChannels would benefit from being able to process the data and send data from a Worker.  An example of this is a game which handles state updates and other processing in a Worker, keeping the mainthread application free to handle rendering and UI interactions, and avoiding or minimizing GC pauses.

Basic Mechanism:
The RTCDataChannel would be a transferrable object, which can be sent via postMessage:

  channel = createDataChannel("MyChannel", {});
  // or we're in an ondatachannel callback/event triggered by the other
  // side creating an RTCDataChannel
  worker.postMessage(channel, [channel]);
  // channel is now owned by the worker; no more events will occur on the
  // sender's version of 'channel'

The worker will receive the object, and can set event handlers on it.

Handling of Events:
After a transfer, all events occur in the worker, and the worker must set up event handlers to process them.  Any events that occur during the transfer, or that were queued to be fired in the sender, will be held until the worker gets the transferred object.  This means the worker should set EventHandlers on the channel immediately on receiving the channel.

Close:
The worker can call channel.close(), which will operate normally. If the PeerConnection is shut down via peerconnection.close(), or if the RTCDataChannel m=application line is renegotiated 'off', then the worker will receive a close event for the channel, as normal.

An RTCDataChannel may be transferred at any time, and may be transferred more than once.
(Reporter)

Updated

3 years ago
backlog: --- → webrtc/webaudio+
Rank: 25
Keywords: dev-doc-needed
(Reporter)

Updated

3 years ago
Rank: 25 → 15
Priority: P2 → P1
Rank: 15 → 23
Priority: P1 → P2
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.