reliable
reliable copied to clipboard
michelle
Slow but reliable transport for unreliable DataChannels.
It's not a complete re-desing, but only some tune-ups to help compatibility and improve of my DataChannel-polyfill. All the management to work as a polyfill is there (https://github.com/piranna/DataChannel-polyfill/commit/bf63d0d684e70a6077e901dc3bfc9e56fa06653e), although would...
According to http://dev.w3.org/2011/webrtc/editor/webrtc.html#peer-to-peer-data-api (June 3th), now DataChannels has removed the 'reliable' atribute and it's using ordered, maxRetransmitTime, maxRetransmits, protocol, negotiated and id. Reliable library should have a way to define...
When trying to send an image of just some KB, the content gets converted to a sequence of escaped Unicode glyphs (\"u1234") getting a transfered size sometimes more than double...
Perhaps there is a more optimal way to queue up messages to be sent, so that messages that CAN be sent right away will. Maybe 2 queues? Cache the stringification...
Adapt the code to work as a polyfill for DataChannels (instead of creating a new object that wrapps a DataChannel object) so code developed using it can be future proof...