Re: [whatwg/fetch] Trailer support in the API (#981)

I would think the point of trailers is that they can be computed after streaming the response body, so specifying them to the response constructor wouldn't be what we want. If you know the trailer values at constructor time, you might as well make them headers instead.

Also, on the receiving side, if `response.trailers()` is invoked before the response body has been read, what happens to the body? Does it get buffered in RAM? I think it's important to design the API to avoid accidental buffering of entire responses.

I'm less concerned about the impact on deferred proxying in `workerd` -- this would just be a case where deferred proxying optimization can't take effect, similar to what happens when using the streams API to generate a response body.

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

Message ID: <whatwg/fetch/issues/981/1642705082@github.com>