- From: Chris Palmer <palmer@google.com>
- Date: Wed, 10 Dec 2014 11:34:32 -0800
- To: 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 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). I don't claim that this is definitive, but you can see a fun demo at: https://www.httpvshttps.com/ For me and a lot of people, HTTPS (HTTP/2) is consistently lower latency than HTTP in that demo.
Received on Wednesday, 10 December 2014 19:35:00 UTC