Re: [server-timing] first run at spec draft

On top of what we discussed during the call, do you know of any browser
that intends to implement trailer support. Currently it seems like there is no
support for it <http://www.browserscope.org/?category=network>.

Also - regarding syntax, if I'm reading it correctly, why are metric and
description optional?
And what's the use case to enable multiple descriptions on a single metric?

On Tue, Feb 3, 2015 at 9:19 PM, Ilya Grigorik <igrigorik@google.com> wrote:

> https://w3c.github.io/server-timing/
>
> - metrics are communicated via Server-Timing header field
> - each metric is represented as a ServerEntry (extends PerformanceEntry)
> - metrics are accessed via same API as NT/RT: same interface extensions,
> global buffer, etc.
>
> For a hands-on overview checkout:
> - https://w3c.github.io/server-timing/#examples
> - https://w3c.github.io/server-timing/#use-cases
>
> Would appreciate any thoughts and/or feedback! Does it look reasonable,
> any objections to proposed interface?
>
> ig
>