Clever Geek Handbook

Usrsctp send buffer does not free itself

We are working with the webrtc C ++ data feeds library and in our

The receiving side (JS webpage) does indeed receive all bytes we sent until an error is found. It is also worth noting that this only happens when we try to send data from a C ++ application to JS, not the other way around. We tried to look back at mozilla but can't seem to draw any conclusions about what the problem is about.

+3


source to share


1 answer


It is difficult to answer such a question straight away. I would start looking into wireshark traces to make sure that your remote side (JS page) is actually validating the data you are sending (for example if chunks of SACK are sent back) and what is the value of the received buffer (a_rwnd) specified in those SACKs. This may not be a problem on your side, but you only get EWOULDBLOCKS because the SCTP originating side cannot clear the data from the buffers because it is still waiting for a delivery confirmation from the remote end. Please provide more details about your case, also provide sample code for your JS page if possible.



+1


source






More articles:


All Articles