+
Skip to content

Conversation

sosthene-nitrokey
Copy link
Contributor

@sosthene-nitrokey sosthene-nitrokey commented Feb 3, 2025

Not fully implemented, probably should be using a custom structure for TcpKeepalive to avoid exposing socket2 publicly.

In that case, should we have the same feature flag as the socket2 library? Or should we allow each setting and just warn when one is not available for the given platform ?

Fixes #547

Not fully implemented, probably should be using a custom
structure for `TcpKeepalive` to avoid exposing `socket2` publicly.

In that case, should we have the same feature flag as the `socket2` library?
Or should we allow each setting and just warn when one is not available for the
given platform ?
@algesten
Copy link
Owner

algesten commented Feb 3, 2025

Are there other things we might want to tweak using socket2? The only thing I'm hesitating about is the name of the keepalive since we might want one more generic tcp-extra or something.

If this lands in std::net eventually, we can make the feature flags a no-op, but it'd be nice to not have many many flags in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add TCP keep-alive?

2 participants

点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载