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
When developing, understanding delays is helpful. The document references various delays and waits, but consolidating them into a single section could make it clearer. A dedicated section on expected reconnection times would also be useful from a developer’s perspective, perhaps even with a flowchart to illustrate the process.
Most of the time is spent waiting for a DHCP lease, the reset happens very quickly.
For outbound connections, it might also be worth covering a simple reconnection strategy, like exponential back-off, to improve robustness, especially while the stack is still evolving.
The text was updated successfully, but these errors were encountered:
adam-3bian
changed the title
Networking: Consolidate Reconnection Delays
Networking: Consolidate Reconnection Delays.
Jan 30, 2025
adam-3bian
changed the title
Networking: Consolidate Reconnection Delays.
Networking: Consolidate reconnection delays.
Jan 30, 2025
adam-3bian
changed the title
Networking: Consolidate reconnection delays.
Networking: Consolidate waits/delays.
Jan 30, 2025
I don't think these line numbers go where you think they do: they don't seem to line up with the comments. Can you use the permalink button so that they're linked to a specific git version (and I can then figure out where the text ended up)?
When developing, understanding delays is helpful. The document references various delays and waits, but consolidating them into a single section could make it clearer. A dedicated section on expected reconnection times would also be useful from a developer’s perspective, perhaps even with a flowchart to illustrate the process.
book/text/networking.tex
Line 597 in 0394c53
book/text/networking.tex
Line 925 in 0394c53
For outbound connections, it might also be worth covering a simple reconnection strategy, like exponential back-off, to improve robustness, especially while the stack is still evolving.
The text was updated successfully, but these errors were encountered: