RTCDataChannel
Related Doc:
package dom
The EventTarget.addEventListener() method registers the specified listener on the EventTarget it's called on.
The EventTarget.addEventListener() method registers the specified listener on the EventTarget it's called on. The event target may be an Element in a document, the Document itself, a Window, or any other object that supports events (such as XMLHttpRequest).
This implementation accepts a settings object of type EventListenerOptions.
The EventTarget.addEventListener() method registers the specified listener on the EventTarget it's called on.
The EventTarget.addEventListener() method registers the specified listener on the EventTarget it's called on. The event target may be an Element in a document, the Document itself, a Window, or any other object that supports events (such as XMLHttpRequest).
Returns a DOMString indicating the type of binary data transmitted by the connection.
Returns a DOMString indicating the type of binary data transmitted by the connection. This should be either "blob" if Blob objects are being used or "arraybuffer" if ArrayBuffer objects are being used. Initially it is set to "blob".
It controls the type of the MessageEvent.data property passed in the parameter of message targetting this RTCDataChannel.
Returns an unsigned long containing the amount of bytes that have been queued for sending: that is the amount of data requested to be transmitted via RTCDataChannel.send() that has not been sent yet.
Returns an unsigned long containing the amount of bytes that have been queued for sending: that is the amount of data requested to be transmitted via RTCDataChannel.send() that has not been sent yet. Note that if the channel state, as given by RTCDataChannel.readyState is "closed", the buffering continues.
Dispatches an Event at the specified EventTarget, invoking the affected EventListeners in the appropriate order.
Dispatches an Event at the specified EventTarget, invoking the affected EventListeners in the appropriate order. The normal event processing rules (including the capturing and optional bubbling phase) apply to events dispatched manually with dispatchEvent().
Returns an unsigned short being a unique id for the channel.
Returns an unsigned short being a unique id for the channel. It is set at the creation of the RTCDataChannel object.
Returns a DOMString containing a name describing the data channel.
Returns a DOMString containing a name describing the data channel. There is no constraint of uniqueness about it.
Is the event handler called when the close event is received.
Is the event handler called when the close event is received. Such an event is sent when the underlying data transport has been closed.
Is the event handler called when the message event is received.
Is the event handler called when the message event is received. Such an event is sent when a message is available on the data connection.
The read-only property RTCDataChannel.ordered returns a Boolean indicating if the order of delivery of the messages is guaranteed or not.
Returns a DOMString containing the name of the subprotocol in use.
Returns a DOMString containing the name of the subprotocol in use. If none, it returns "".
Returns an enum of the type RTCDataChannelState representing the state of the underlying data connection.
Removes the event listener previously registered with EventTarget.addEventListener.
Removes the event listener previously registered with EventTarget.addEventListener.
This implementation accepts a settings object of type EventListenerOptions.
Removes the event listener previously registered with EventTarget.addEventListener.
Removes the event listener previously registered with EventTarget.addEventListener.
Sends the data in parameter over the channel.
Sends the data in parameter over the channel. The data can be a DOMString, a Blob, an ArrayBuffer or an ArrayBufferView.
The RTCDataChannel interface represents a bi-directional data channel between two peers of a connection.