From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: http/2 and Emacs Date: Sat, 20 Feb 2016 08:55:18 -0800 Organization: UCLA Computer Science Department Message-ID: <56C89A76.7070401@cs.ucla.edu> References: <87lh6h6vfg.fsf@gnus.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1455987363 24663 80.91.229.3 (20 Feb 2016 16:56:03 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 20 Feb 2016 16:56:03 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Feb 20 17:55:50 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aXAou-0006y7-Av for ged-emacs-devel@m.gmane.org; Sat, 20 Feb 2016 17:55:48 +0100 Original-Received: from localhost ([::1]:34065 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXAos-0007Dk-Kv for ged-emacs-devel@m.gmane.org; Sat, 20 Feb 2016 11:55:46 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43746) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXAoW-0007De-Uu for emacs-devel@gnu.org; Sat, 20 Feb 2016 11:55:25 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aXAoT-0005Pm-Pb for emacs-devel@gnu.org; Sat, 20 Feb 2016 11:55:24 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:42959) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aXAoT-0005Pi-K3 for emacs-devel@gnu.org; Sat, 20 Feb 2016 11:55:21 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id C62BD160FEF for ; Sat, 20 Feb 2016 08:55:19 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id SnafNP2-xQMF for ; Sat, 20 Feb 2016 08:55:19 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 10F28160FF0 for ; Sat, 20 Feb 2016 08:55:19 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 9WVMvOLJj4sO for ; Sat, 20 Feb 2016 08:55:18 -0800 (PST) Original-Received: from [192.168.1.9] (pool-100-32-155-148.lsanca.fios.verizon.net [100.32.155.148]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id E928E160FEF for ; Sat, 20 Feb 2016 08:55:18 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:200326 Archived-At: Richard Stallman wrote: > I don't know the name "SPDY". SPDY is/was an experimental protocol developed by Google, intended as a replacement for HTTP that would reduce page load times. It has morphed into HTTP/2, which is specified by Internet RFC 7540 (May 2015). HTTP/2 is supported by high-volume web sites such as Google and Facebook. Google says about 25% of resources in the Chrome browser are now served over HTTP/2, and w3techs says about 6.5% of public websites support HTTP/2, up from about 2.5% of websites at the end of 2015. The basic idea of HTTP/2, as the RFC states, is that it: "allows interleaving of request and response messages on the same connection and uses an efficient coding for HTTP header fields. It also allows prioritization of requests, letting more important requests complete more quickly, further improving performance. The resulting protocol is more friendly to the network because fewer TCP connections can be used in comparison to HTTP/1.x.... Finally, HTTP/2 also enables more efficient processing of messages through use of binary message framing." HTTP/2 connections are typically encrypted rather than plaintext. This is both for security and to speed performance (avoids a roundtrip negotiation). HTTP/2 also allows server push. One downside is that HTTP/2 is more of a pain to debug, because of its use of multiplexing, compression, encryption, and binary formats. Debugging is doable, but the standard debugging tools haven't caught up yet.