Make spdystream.Stream implement io.WriteTo or io.ReaderFrom interface
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 149
- Forks
- 59
- PR merge metrics
- No merged PRs in 30d
Description
io.Copy currently copies in chunks of 3KB for standard io.Writer and io.Reader implementations, but will instead use io.WriteTo or io.ReadFrom if the writer or reader supports the relevant method. To improve the performance of copying to/from spdystream.Stream, we can tweak the chunk size by implementing these methods.
We currently use io.Copy for spdystream.Stream in docker/libchan to handle transparent stream passing, so this could potentially improve the performance of libchan over spdy.
See io.Copy source for reference.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the spdystream.Stream implementation and review how io.Copy is used for stream passing in docker/libchan. Check the io.Copy reference to understand the relevant interfaces; done means Stream implements io.WriteTo or io.ReaderFrom and copying no longer uses the standard chunked path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100