-
Notifications
You must be signed in to change notification settings - Fork 861
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
Fix extra ack being sent after a connection is established #2832
Conversation
Add an initialization of m_bBufferWasFull to false when starting a connection
Fix guidelines for minimum in flight packets computation
Ah, forgot one thing: if you set this to true in |
That's true, I was focusing on the issue on the transmitter side and forgot about the receiver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The startConnect
function is used by a caller (and probably by a rendezvous), but not by a listener. The variable stays uninitialized for a listener.
@yomnes0 please use the common place for initialization where all other CUDT
member variables are initialized.
Co-authored-by: Maxim Sharabayko <[email protected]>
…n#2832) (uninitialized variable).
…n#2832) (uninitialized variable).
(uninitialized variable).
Add an initialization of m_bBufferWasFull to false when starting a connection. This will prevent an extra ack from being sent right after the handshake.
Fixes #2829.