W3C home > Mailing lists > Public > www-tag@w3.org > December 2014

Re: Interaction speed Re: Draft finding - "Transitioning the Web to HTTPS"

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 10 Dec 2014 20:52:02 +0100
Message-ID: <5488A462.4050108@gmx.de>
To: Chris Palmer <palmer@google.com>, Tim Berners-Lee <timbl@w3.org>
CC: Tim Bray <tbray@textuality.com>, Marc Fawzi <marc.fawzi@gmail.com>, Bjoern Hoehrmann <derhoermi@gmx.net>, Mark Nottingham <mnot@mnot.net>, Noah Mendelsohn <nrm@arcanedomain.com>, Public TAG List <www-tag@w3.org>
On 2014-12-10 20:34, Chris Palmer wrote:
> On Tue, Dec 9, 2014 at 11:18 PM, Tim Berners-Lee <timbl@w3.org> wrote:
>
>> A result from th early days  of hypertext systems was the rule of thumb was that a user would use a system effectively so long as the response time was 100ms or less.  Any increase of speed below that does not lead to any improvement in problem-solving ability, and increase about would be detrimental, users would tend not to explore as it would not be worth the wait.  So interaction time is critical.
>
> Good news on this front. HTTP/2 (born as SPDY, available today in
> several browsers and servers) is designed to decrease latency and
> round-tripping, even in resource- and request-heavy web apps. And, it
> uses TLS all the time. In fact, end-to-end opacity is necessary for
> its deployment. So users get a speed and safety increase at the same
> time (overall).

That's misleading:

1) HTTP/2 is still pre-IETF-Last-Call

2) The current draft specified HTTP/2 for HTTP URIs, and does that in a 
way that does not require TLS at all.

 > ...


Best regards, Julian
Received on Wednesday, 10 December 2014 19:52:43 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:33:27 UTC