Re: [whatwg/fetch] Consider removing trailers API (#772)

> @igrigorik that's not a request for the generic trailer API though, is it?

What does "generic API" equate to in your head? As discussed previously, ideally what I would like to see is trailer headers be treated as inert (don't impact regular response processing) but readable from Fetch by the application. Specific use cases, like Server-Timing can then build on top of that to provide own layer of functionality.

> Also, how is Server-Timing supposed to work when it ends up in the header block?

Not sure I follow.. As in, non-trailer header block? It would work as it does today.

-- 
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/772#issuecomment-450955572