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

feat: add the retry time interval for sending syn messages #854

Closed
wants to merge 14 commits into from

Conversation

putyWang
Copy link

No description provided.

@putyWang
Copy link
Author

Due to the lack of a retry count and retry time interval for sending syn messages that establish links in the current TCP synSend state, an excessive number of syn link establishment messages will be sent during the link establishment process, and if there is no reply, it will cause messages to be sent continuously. Therefore, I have added the retry time interval (1, 2, 4...) for sending syn messages and the default maximum number of retransmissions (6 times) to the TCP socket timer

Copy link

codecov bot commented Nov 11, 2023

Codecov Report

Merging #854 (6e3511e) into main (9b791ae) will decrease coverage by 0.04%.
The diff coverage is 58.33%.

@@            Coverage Diff             @@
##             main     #854      +/-   ##
==========================================
- Coverage   79.61%   79.58%   -0.04%     
==========================================
  Files          78       78              
  Lines       27890    27921      +31     
==========================================
+ Hits        22206    22222      +16     
- Misses       5684     5699      +15     
Files Coverage Δ
src/socket/tcp.rs 96.44% <58.33%> (-0.25%) ⬇️

📣 Codecov offers a browser extension for seamless coverage viewing on GitHub. Try it in Chrome or Firefox today!

@putyWang putyWang changed the title add 他和 feat: add the retry time interval for sending syn messages Nov 23, 2023
@putyWang putyWang closed this Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant