connection: Don't double-buffer TCP stream #102
Merged
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.
UnsecuredStream doesn't need to be wrapped in a BufWriter since write_all() passes the entire buffer-to-send to the underlying TCP stream.1 And it doesn't need to be wrapped in a BufReader since HttpStreamBytes (in response.rs) wraps the whole HttpStream in a BufReader. Both of these cases cause us to use a little extra memory and copy bytes twice when we only need to copy once.