Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upInvestigage full-duplex request/response streaming #26905
Labels
Comments
|
A few pointers: In
Then later, this future is used to:
I guess the question is really whether Hyper gives us the headers, and data, for the response, while the request stream is still being read from... |
|
Looking at https://docs.rs/hyper/0.13.6/src/hyper/client/mod.rs.html#245 I have a feeling using the response future requires first completing the request feature, meaning it would not work... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See the discussions over at whatwg/fetch#425 (comment)
The idea is, I think, that the body of a request would be transmitted over the network, and at the same time the body of the response could already be read by script as a stream.
From the linked-to discussion, it appears web developers want this, and the spec sort of allows for it(?), however current implementations have a hard time changing their networking stack model to allow for this.
I think we should be able to do it, since #25873 has landed, and I don't think there is anything in the structure of
netthat would prevent this.However first we need to investigate #26904, and then I think it would be interesting to see if Servo could support full-duplex streaming.