Re: SPDY Review

Julian Reschke <julian.reschke@gmx.de> Thu, 07 June 2012 16:35 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDD6B21F8826 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 7 Jun 2012 09:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.932
X-Spam-Level:
X-Spam-Status: No, score=-7.932 tagged_above=-999 required=5 tests=[AWL=2.667, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I2J0CXmoDLOe for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 7 Jun 2012 09:35:26 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 4340621F86E3 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 7 Jun 2012 09:35:26 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Scffa-0007XE-7v for ietf-http-wg-dist@listhub.w3.org; Thu, 07 Jun 2012 16:34:46 +0000
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <julian.reschke@gmx.de>) id 1ScffQ-0007W7-PY for ietf-http-wg@listhub.w3.org; Thu, 07 Jun 2012 16:34:36 +0000
Received: from mailout-de.gmx.net ([213.165.64.22]) by lisa.w3.org with smtp (Exim 4.72) (envelope-from <julian.reschke@gmx.de>) id 1ScffN-0003VX-BI for ietf-http-wg@w3.org; Thu, 07 Jun 2012 16:34:35 +0000
Received: (qmail invoked by alias); 07 Jun 2012 16:34:06 -0000
Received: from p5DD972CB.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.114.203] by mail.gmx.net (mp016) with SMTP; 07 Jun 2012 18:34:06 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19Rv/QidWZR67UO5QsBHe1eJb0y/Bymtdxg74w6Sm RmUf9MACB6v0at
Message-ID: <4FD0D7E6.50403@gmx.de>
Date: Thu, 07 Jun 2012 18:33:42 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120604 Thunderbird/13.0
MIME-Version: 1.0
To: Martin Nilsson <nilsson@opera.com>
CC: ietf-http-wg@w3.org
References: <op.wfjd0s2diw9drz@riaa>
In-Reply-To: <op.wfjd0s2diw9drz@riaa>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Received-SPF: pass client-ip=213.165.64.22; envelope-from=julian.reschke@gmx.de; helo=mailout-de.gmx.net
X-W3C-Hub-Spam-Status: No, score=-1.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1ScffN-0003VX-BI 0db4d3e1f46bd9740df8a47bd8890889
X-Original-To: ietf-http-wg@w3.org
Subject: Re: SPDY Review
Archived-At: <http://www.w3.org/mid/4FD0D7E6.50403@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/13637
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
Resent-Message-Id: <E1Scffa-0007XE-7v@frink.w3.org>
Resent-Date: Thu, 07 Jun 2012 16:34:46 +0000

On 2012-06-07 16:18, Martin Nilsson wrote:
> ...
> 2.1. Pipelining & response order
>
>    Pipelining is very important to avoid the overhead of setting up new
>    TCP connections. Limiting the number of connections is also
>    beneficial for congestion control. HTTP pipelining is defined in
>    HTTP 1.1 and Opera has spent considerable effort to make it work as
>    widely as possible. Unfortunately quite a lot of equipment doesn't
>    implement HTTP 1.1 correctly, so lots of heuristics has to be
>    applied in real world scenarios.
>
>    Given the non-uniform response times of different requests from the
>    same server, due to different amount of backend work required to
>    generate a response, pipelining is prone to stalling when a slow
>    request blocks a faster request. Out-of-order response is a good
>    solution to the problem. It can easily be added to HTTP by adding a
>    request ID header in each request and expecting corresponding
>    response IDs in the responses.
> ...

Note: that doesn't work with caching.

But see the Assoc-Req header field described in 
<http://tools.ietf.org/html/draft-nottingham-http-pipeline-00#section-5> 
-- I think it's experimentally implemented in Firefox (which means it 
needs a spec :-)

Best regards, Julian