feat(net): add socket timeouts to Server and Client #621
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While these methods are marked unstable in libstd, this is behind a
feature flag,
timeouts
. The Client and Server both haveset_read_timeout
andset_write_timeout
methods, that will affect allconnections with that entity.
BREAKING CHANGE: Any custom implementation of NetworkStream must now
implement
set_read_timeout
andset_write_timeout
, so those willbreak. Most users who only use the provided streams should work with
no changes needed.
Closes #315
@reem r?