- From: Sigbjørn Vik <sigbjorn@opera.com>
- Date: Mon, 29 Nov 2010 10:57:33 +0100
- To: public-web-perf@w3.org
On Wed, 24 Nov 2010 22:02:07 +0100, Christian Biesinger <cbiesinger@gmail.com> wrote: > Hi all, > > while implementing some of the networking support for webtiming in > Firefox, I noticed this requirement: > >> connectEnd must include the time interval to establish the transport >> connection. It must not include other time interval such as SSL >> handshake and SOCKS authentication. > > This is fairly hard to implement in Firefox because due to how the > abstractions work, SSL handshake is considered part of connect(). > > Do other UAs have an easier time implementing this attribute as > specified? Should the spec be changed? Quote from a relevant developer: "It shouldn't really be that difficult, but it would be a little easier to simply time the whole connection." Since we are on the subject anyhow, do we want to provide timing information for the handshake itself? This could be quite useful information, and information which really cannot be gleaned from anywhere else. There have been big studies going as to see how much performance is lost when enabling SSL, this timing information would be of great value in such cases. If we need to put in timers between connectionEnd and handshakeStart in any case, it also shouldn't be much extra work to explicitly add handshake timers. -- Sigbjørn Vik Quality Assurance Opera Software
Received on Monday, 29 November 2010 09:57:57 UTC