On Tue, Nov 18, 2014 at 12:11 AM, Anne van Kesteren <ann...@annevk.nl>
wrote:
> On Mon, Nov 17, 2014 at 3:50 PM, Domenic Denicola <d...@domenic.me> wrote:
> > What do we think of that kind of behavior for fetch requests?
>
> I'm not sure we want to give a potential hostile piece of script that
> much control over what goes out. Being able to lie about
> Content-Length would be a new feature that does not really seem
> desirable. Streaming should probably imply chunked given that.
>
Agreed.
stream.write(new ArrayBuffer(1024));
> setTimeout(() => stream.write(new ArrayBuffer(1024)), 100);
> setTimeout(() => stream.write(new ArrayBuffer(1024)), 200);
> setTimeout(() => stream.close(), 300);
And, for abort(), underlying transport will be destroyed. For TCP FIN
without last-chunk. For http2 maybe RST_STREAM with INTERNAL_ERROR? Need
consult httpbis.
