You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Windows if I set the send and receive buffers of a TCP socket to something like 7000 and then fetch the value it comes out as 7000, but on linux fetching the value returns 16384. I'm guessing these buffer sizes are more of a suggestion to the OS and its free to choose a different value. So, should our API recognise this? Might be be better to have these functions return the value which was set, similar to how write functions return how many bytes were actually sent vs what you offered.
The text was updated successfully, but these errors were encountered:
On Windows if I set the send and receive buffers of a TCP socket to something like 7000 and then fetch the value it comes out as 7000, but on linux fetching the value returns 16384. I'm guessing these buffer sizes are more of a suggestion to the OS and its free to choose a different value. So, should our API recognise this? Might be be better to have these functions return the value which was set, similar to how write functions return how many bytes were actually sent vs what you offered.
The text was updated successfully, but these errors were encountered: