On 14 July 2014 17:17, Domenic Denicola <dome...@domenicdenicola.com> wrote:
> From: Juan Ignacio Dopazo <jdop...@yahoo-inc.com> > > > I agree that Node's design sounds a bit better for piping. But where > would you put the FetchResponseBodyStream? fetch() returns a promise for a > Response. Why would the response have a writable stream for the request? > There are two options: > > > > 1- Have fetch() return a promise for an object with "request" and > "response" properties > > 2- Have fetch() return something that is not a promise > > 3- have fetch() take a writable stream as a parameter, e.g. > > var request = new Request("http://example.com", { method: "POST" }); > myReadableStream.pipeTo(request.body); > fetch(request); > > (this is not great ergonomically, but seems to be the direction the > current API points to...) The current API is var request = new Request("http://example.com", { method: "POST", body: myReadableStream });