-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incoming payloads are silently truncated to 8kB #365
Comments
This is a known problem with the WebRTC API itself. It doesn't provide a good way to handle large messages. All implementations have some limitation. We can increase the default payload size but it would still be an arbitrary limit. A possible solution would be to make this configurable. |
I still think there should be some sort of indication given to the application that the message has been truncated. |
I'm confused — your link speaks of a protocol problem with SCTP, not an API problem. Couldn't the |
I'm glad to report that Detach solved my problem quite nicely. Thanks. |
I agree we should look into adding a warning. We'll keep the issue open untill then. |
FYI, I did indeed link the wrong info above. For truly sending/receiving any size messages via the WebRTC API, it would have to be extended as suggested in w3c/webrtc-pc#1732. |
Relates to pion/webrtc#365
Relates to pion/webrtc#365
If incoming payloads are larger than 8kB, they are silently truncated, which causes loss of data. I believe that there are two issues here:
A simple workaround is to increase the value of
receiveMTU
inrtcpeerconnection.go
¸ but that's obviously not satisfactory.The text was updated successfully, but these errors were encountered: