Re: Implementing the web timing spec

On Sun, Mar 14, 2010 at 2:24 PM, Georg Maaß <[email protected]> wrote:

> Srirang Doddihal wrote:
>
>> 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.
>>
>
> DNS time, connect time and so on is information that is interesting for the
> end user, who may switch collecting this information on or off.


It's not just the end user who is interested in this. A lot (most?) of
people hosting webapps ask for this information.

It should be off by default and should never be accessible to none chrome
> because this is sensible information.
>

Why would you classify this as sensible information?


>
> It is useful for service technicians to find out, why internet does not
> work, but the question is, why must this analysis tool be part of the
> browser? It has nothing to do with web application and therefore must not be
> part of the DOM, because it is not part of the document.


This information is necessary to understand the end to end
behavior/performance of  the web app as seen by the end user. So this is not
for technicians trying to troubleshoot a connectivity problem, but this is
for people hosting the websites who want to know the QoS as seen by their
end users. Only the browser can provide this information to the website and
DOM is probably the best way to expose this information in a standard
manner.

We all know that client side technicians have various tools, which are far
more powerful than the browser, to find out why internet does not work.


> _______________________________________________
> 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.