Re: [whatwg/fetch] Request body streams that cannot be retried (#538) from Dragana Damjanovic on 2019-11-15 (public-webapps-github@w3.org from November 2019)

From: Dragana Damjanovic <notifications@github.com>
Date: Fri, 15 Nov 2019 01:30:00 -0800
To: whatwg/fetch <fetch@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <whatwg/fetch/issues/538/554283392@github.com>

> I also think we likely want to allow replaying the data if an error is received soon, since this is an inevitable thing that can happen if a browser reuses sockets, and a server times old sockets out.

I think this is specific to network stack, it desides to send data on reused connection and it may happen that connection has been closed already and therefore data needs to replayed. (it is somewhat network optimization with a risk that data needs to be replayed). I think API should not need to worry about this. Maybe just a comment in the spec that this may happen is enough. Also 0-rtt replays are specifics of the networking protocols and api should not worry about it.


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/538#issuecomment-554283392

Received on Friday, 15 November 2019 09:30:02 UTC