New example datachannel buffer limits #5
   Merged  
   Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.    
 
This PR adds a new example to the list that sends a given amount of data over a
RTCDataChanneland gets it back.It's basically like the ping/pong example with two variables:
Data is chunked into pieces, which are queued to be sent over the
RTCDataChannel, and depending on the browser's maximum buffer send value (and also in the underlyingusrsctplibrary) or even on the chunk size, you may or may not be allowed to send a given amount of data.This example just puts in evidence, hopefully in a convenient way and using
node-webrtc, what has been well described in various places:Can also provide some form of answer to node-webrtc/node-webrtc#464
Hope this helps!