Skip to content
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

Disable socket receive buffer, unless USE_RECV_BEFORE_SEND_WORKAROUND… #10961

Closed
wants to merge 1 commit into from

Conversation

icing
Copy link
Contributor

@icing icing commented Apr 13, 2023

… is in place

While we would like to use this, we have stalls in parallel transfers where not all buffered data is consumed and no socket events happen.

… is in place

While we would like to use this, we have stalls in parallel
transfers where not all buffered data is consumed and no
socket events happen.
@jay
Copy link
Member

jay commented Apr 14, 2023

Thanks. This is a difficult and time consuming area.

bch pushed a commit to bch/curl that referenced this pull request Jul 19, 2023
- Disable socket receive buffer unless USE_RECV_BEFORE_SEND_WORKAROUND
  is in place.

While we would like to use the receive buffer, we have stalls in
parallel transfers where not all buffered data is consumed and no socket
events happen.

Note USE_RECV_BEFORE_SEND_WORKAROUND is a Windows sockets workaround
that has been disabled by default since b4b6e4f, due to other bugs.

Closes curl#10961
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

None yet

2 participants