Opens an outbound data channel to peerId.
Identifier of the remote peer to open a channel to.
Channel label; the transfer engine encodes routing information here.
Optionalopts: RTCDataChannelInitOptional RTCDataChannel configuration (the engine requests ordered: true).
The new channel, or undefined if there is no active connection to peerId.
Removes a previously registered data-channel listener.
Always 'data-channel'.
The exact handler reference passed to DataChannelHub.on.
Subscribes to remotely-initiated data channels.
Always 'data-channel'.
Invoked with the originating peer id and the newly opened channel.
Abstraction over the peer connection layer that the file-transfer engine uses to open and receive RTCDataChannels.
This is the integration seam between the file-transfer module and whatever manages the underlying
RTCPeerConnections (for example an application's call/mesh layer). A FileTransferManager opens outbound channels through it and listens for inbound ones to drive the transfer protocol.Remarks
Data channels carry two kinds of traffic: a single JSON control channel per peer (labelled CONTROL_CHANNEL_LABEL) and one or more binary chunk channels per transfer (labelled via dataChannelLabel). Implementations should surface every remotely-initiated channel through the
data-channelevent.