- From: Ben Kelly <notifications@github.com>
- Date: Mon, 15 Mar 2021 09:08:22 -0700
- To: w3c/ServiceWorker <ServiceWorker@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Monday, 15 March 2021 16:08:39 UTC
When a response is passed to respondWith() most (all?) browsers will end up serializing the body through some kind of data pipe with a fixed capacity. This means that a response constructed with a ReadableStream body may see the data chunks get re-buffered into different size chunks on the other side. It would be nice if the spec captured this in some way. Perhaps as a note if it can't really be represented in normative text. Not sure if this should be here or in fetch. cc @annevk -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/ServiceWorker/issues/1573
Received on Monday, 15 March 2021 16:08:39 UTC