RE: [ResourceTiming] Wire Protocol

Seeing that all major browser vendors now have some SPDY implementation, it seems reasonable that we should consider adding wire protocol information to Resource Timing L2 spec. Whether this new attribute returns HTTP2, SPDY1/2/3, or something else should be discussed.


-----Original Message-----
From: Nottingham, Mark [] 
Sent: Monday, September 2, 2013 9:42 PM
To: public-web-perf
Subject: [ResourceTiming] Wire Protocol


Previously, there have been requests [1] to add information to ResourceTiming about the wire protocol used in fetches, in particular for SPDY.

There was a bit of discussion, but it seemed to stop here [2]:

> I think it's too early to add spdy/http2 vs. http given that the protocol is still in works.

HTTP/2.0 [3] is now seeing early implementation [4]. Since the focus of HTTP/2.0 is performance, having metrics about how it is performing is critical to evaluate its effectiveness and aid its adoption.

Is it really the intent of the WG to wait until the protocol is no longer "still in the works" before adding a metrics for it? 

I'm happy to make a detailed proposal if that will help unblock this...



Mark Nottingham

Received on Wednesday, 4 September 2013 16:34:01 UTC