Serialization of larger payloads can lead to incorrect chunks

pvheiningen commented 3 years ago

This PR contains a fix for issue https://github.com/KallDrexx/rust-media-libs/issues/21.

It contains the following changes:

Changed the size of the socket send buffer to 4MB (from default: 87 KB)
Changed the size of the socket receive buffer to 4MB (from default: 369 KB)
Changed the 'write' function to 'write_all', which will fail when the buffer is not fully written.

Gstreamer uses a default size of the TCP buffers of 2.5MB, I set the default sizes to 4 MB.

I'm not a Rust programmer, so let me know what you would like to see changed!

KallDrexx commented 3 years ago

What's really interesting about this is that the normal Rust TCP structs have no way to get or receive TCP buffer size. I wonder if I missed this because this is primarily a concern in event event driven networking, as I see the capability in both Tokio and Mio's APIs.

Thanks a ton for this!

pvheiningen commented 3 years ago

Thank you for a great library!

KallDrexx / rust-media-libs

Serialization of larger payloads can lead to incorrect chunks #22