On Thursday, November 29, 2012 at 4:54 PM, Patrick Reilly wrote:
<snipped>
Notice that it's got the SHA-1 hash of the original string prepended with a colon colon as a separator.
— Patrick
Back in July I tried to read through parts of Google Analytics's obfuscated ga.js, which had recently added page performance analytics. Rather than send the absolute timestamps, they calculate the following deltas and pack them into an array:
timing.loadEventStart - timing.navigationStart, timing.domainLookupEnd - timing.domainLookupStart, timing.connectEnd - timing.connectStart, timing.responseStart - timing.requestStart, timing.responseEnd - timing.responseStart, timing.fetchStart - timing.navigationStart
(A timer polls navigationStart and grabs these data points as soon as navigationStart is nonzero.)
I think we ought to read the specs carefully and experiment a little until we figure out precisely what each of these intervals measures and what sort of things it can usefully indicate. It would be good to come up with descriptive names for each of them.
If you want to give it a shot, you can use this gist to get the data in a way that won't break things on older browsers: https://gist.github.com/4174695
-O