Re: Implementing the web timing spec

cc'ing Zhiheng, the spec editor, which I should've done in the first place

Boris Zbarsky wrote:
> On 2/11/10 1:28 PM, Christian Biesinger wrote:
>> Would people agree this is useful, and in particular, would the DOM
>> peers be willing to accept patches to implement this spec?
> 
> So the biggest issue I see here (past the fact that I'm not sure we can 
> sanely get some of this information) is that any element that exposes 
> this interface ends up bigger by about 100 bytes, right?  That seems a 
> little unfortunate....

That is unfortunate, but there's optimization you can do - instead of 
storing the timestamps as msec-since-epoch, you could store the startup 
timestamp once, and only store the differences to that, for which a 
PRUint32 might suffice. Or you can use the document-load-start timestamp 
instead of startup. That way, you only need half the memory.

You could further optimize and instead of storing start+end, store only 
the difference, which might be good enough.

-christian