On Fri, 2014-11-07 at 14:00 -0800, Ilya Grigorik wrote: > https://gist.github.com/igrigorik/97dfe5ea9b4a85162e25 > > We had a brief discussion around this at TPAC, but in the context of > extending User Timing. However, having thought about it some more, I'm > thinking this could/should be an extension for Nav and Resource Timing > interfaces... perhaps even a standalone spec? > > That said, I'm getting ahead of myself... Curious to hear everyone's > thoughts? Is it worth pursuing further? Am I overlooking any major problems > or gotchas?
I said last week that I would look into the charter [1] to see if this is is in scope or not. Right now, the closest I was able to find in our charter is the following sentence associated with resource timing: "The user agent captures the end to end latency associated with loading resources from a web server". So one could claim that server timing could be done as part of resource timing itself and, as such, we could do a separate document while we're at it. So, I'm inclined to say that server timing is indeed in scope and we don't need a revised charter in order to publish it. If anyone disagrees, please let me know and I'll simply come up with a new proposed charter to include it. Philippe [1] http://www.w3.org/2013/01/webperf.html
