Skip to content

doc: clarify sub-1000ms behavior in socket.setKeepAlive #65869

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.

Sign up for GitHub

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

Open
haramj wants to merge 1 commit into
base: main
Choose a base branch
from
+3 −1
Open

doc: clarify sub-1000ms behavior in socket.setKeepAlive #65869

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion doc/api/net.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1669,7 +1669,9 @@ corresponding system default unchanged.

`initialDelay` and `interval` are specified in milliseconds but the
underlying socket options are configured in whole seconds; the values are
divided by `1000` and rounded down before being applied.
divided by `1000` and rounded down before being applied. For example,
setting `initialDelay` to `400` will result in a `TCP_KEEPIDLE` of `0`
seconds (since `400 / 1000` rounds down to `0`).

Enabling the keep-alive functionality will set the following socket options:

Expand Down
Loading