rawrtc-data-channel
rawrtc-data-channel copied to clipboard
rawrtc
A standalone WebRTC and ORTC data channel implementation.
To Do: * [x] API additions - [x] `rawrtc_sctp_context` - [x] DTLS role getter - [x] DTLS transport state getter - [x] SCTP transport detach (from DTLS transport) handler -...
That should be `min(negotiated_incoming_streams, negotiated_outgoing_streams)`.
Investigate if this is true!
A channel with the equivalent of `maxPacketLifeTime` should also add the time of buffering when enqueuing messages, so messages are discarded as expected.
Currently we do send all queued data but I believe we incorrectly send it even after the outgoing stream has been reset. This will require having an outgoing queue per...
Creating data channels is not allowed before the DTLS transport is connected to be able to determine a stream id (which uses even/odd rule depending on the DTLS role). Being...
The application can currently receive partial messages (using the streaming mode) but cannot send them in a partial manner.
This makes it possible to interleave messages on different streams. It requires separate buffers for each data channel and a scheduler to handle the pending messages fairly.
The redirect transport passes inbound data into a raw socket after some header alteration (since the SCTP port may change, the checksum needs to be recalculated). That's pretty much all...