Re: [whatwg/fetch] Add server-timing to timing info struct (PR #1406)

> "So dealing with them in trailer headers doesn't have implementer agreement?" is something I'd still like an answer to. The note also doesn't tackle this adequately I think as trailers can be received at a much later point so you probably want a separate data structure for them.

I don't think that would be necessary. Resource timing is only reported after response end, at which point those would be available. But in any case, I would defer this to when there's consensus about trailers.

> 
> I also didn't really mean to ask for note, but rather a comment that indicates we might want to change approach if we end up having to inspect and parse other headers for Resource Timing. At that point it might become better to just pass Resource Timing the header list.

Got it. 


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

Message ID: <whatwg/fetch/pull/1406/c1055413783@github.com>