Re: Implementing the web timing spec

On Sat, Mar 13, 2010 at 8:49 PM, Georg Maaß <[email protected]> wrote:

> Mike Shaver wrote:
>
>> Many pixels have been spent on how to time that very thing reliably,
>> but maybe you're right: why do you think that applications don't need
>> to test the total time for first-time access?  Is that what you're
>> hearing from web developers who are watching the performance of their
>> sites?
>>
>
> Nothing is before Big Bang. Big Bang of a web application is, when the
> first request receives the server. Nothing was before. No one must care
> about the before.
>
> The User sending the request may be interested in that timing and may be
> therefore enable measuring this time. In that case this time from before the
> start may be available, but why should this time be of interest for the
> application? During the application run there are many times to record, why
> is this single before application start of interest? Interesting for the
> application are latencies caused by technical issues and user reaction
> times. So the timing information is needed to distinguish which server side
> waiting is caused by technical issues an what is caused by the user.


You are looking at this only from the web-application point of view. Metrics
like DNS time, connect time and time taken to receive the first byte are
equally important to a lot of people. These numbers tell you how well your
deployment is working.


> _______________________________________________
> dev-tech-dom mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-tech-dom
>



-- 
Regards,
Srirang G Doddihal
Brahmana.

The LIGHT shows the way.
The WISE see it.
The BRAVE walk it.
The PERSISTENT endure and complete it.

I want to do it all ALONE.