- From: Arvind Jain <arvind@google.com>
- Date: Tue, 9 Apr 2013 19:16:28 -0700
- To: Andy Davies <dajdavies@gmail.com>
- Cc: "public-web-perf@w3.org" <public-web-perf@w3.org>
Received on Wednesday, 10 April 2013 02:16:56 UTC
In NavTiming, we say: "connectEnd<https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming2/Overview.html#dom-performancenavigationtiming-connectend> MUST include the time interval to establish the transport connection as well as other time interval such as SSL handshake and SOCKS authentication." It seems it was changed after this discussion: http://lists.w3.org/Archives/Public/public-web-perf/2010Nov/0046.html I don't know if the difference in NavTiming and ResourceTiming is intentional or an oversight. Arvind On Tue, Apr 9, 2013 at 12:16 PM, Andy Davies <dajdavies@gmail.com> wrote: > I understand why the spec states that connectEnd excludes SOCKS > authentication etc., but don't quite understand why it excludes the SSL > Handshake > > "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." > > I've had a hunt back through the archives but I couldn't find any > reference as to why. > > Is anyone able to explain? > > Thanks > > Andy >
Received on Wednesday, 10 April 2013 02:16:56 UTC