Interface DataChannelOptions

When bufferedAmount is above maxBufferedAmount, we pause sending until the bufferedAmountLow event fires - this controls how long we wait for that event in ms

When closing a stream we first send a FIN flag to the remote and wait for a FIN_ACK reply before closing the underlying RTCDataChannel - this controls how long we wait for the acknowledgement in ms

When closing a stream, we wait for bufferedAmount to become 0 before closing the underlying RTCDataChannel - this controls how long we wait in ms

Due to bugs in WebRTC implementations it's necessary for the remote end of the connection to acknowledge the FIN message we send during stream closing. A stream will wait for this many ms.

If the channel's bufferedAmount grows over this amount in bytes, wait for it to drain before sending more data

The maximum message size to be sent over the channel in bytes

When sending the first data message, if the channel is not in the "open" state, wait this long for the "open" event to fire.