From rpenno@juniper.net Thu Dec 3 00:48:26 2009 Return-Path: X-Original-To: ledbat@core3.amsl.com Delivered-To: ledbat@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8F14E3A68AD for ; Thu, 3 Dec 2009 00:48:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.599 X-Spam-Level: X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DWQeXHsb2tcm for ; Thu, 3 Dec 2009 00:48:25 -0800 (PST) Received: from exprod7og102.obsmtp.com (exprod7og102.obsmtp.com [64.18.2.157]) by core3.amsl.com (Postfix) with ESMTP id 9F5C93A67E5 for ; Thu, 3 Dec 2009 00:48:22 -0800 (PST) Received: from source ([66.129.224.36]) (using TLSv1) by exprod7ob102.postini.com ([64.18.6.12]) with SMTP ID DSNKSxd7TvO13y7K90WOvdWi7Hoa5DzpSy0t@postini.com; Thu, 03 Dec 2009 00:48:18 PST Received: from p-emfe02-wf.jnpr.net (172.28.145.25) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.1.393.1; Thu, 3 Dec 2009 00:47:09 -0800 Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe02-wf.jnpr.net ([fe80::c126:c633:d2dc:8090%11]) with mapi; Thu, 3 Dec 2009 03:47:08 -0500 From: Reinaldo Penno To: "ledbat@ietf.org" Date: Thu, 3 Dec 2009 03:47:05 -0500 Thread-Topic: HTTP 1.1 Pipelining, Safari and HOL Thread-Index: AcpsSn5cPOQCLwY1RiyMyIekNqoMrQHqrINe Message-ID: In-Reply-To: <50A01DCBF4001B478A524C12CAA7EF4D0FFA71@VENUS.office> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-Entourage/13.0.0.090609 acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [ledbat] HTTP 1.1 Pipelining, Safari and HOL X-BeenThere: ledbat@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: Mailing list of the LEDBAT WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Dec 2009 08:48:26 -0000 During the App Practices and recommendations presentation I mention the fac= t that HTTP clients use many parallel TCP connections to get around the issue of Head of Line Blocking, which is present in HTTP 1.1 Pipelining as well. There was a comment (Stuart?) saying that Safari opens multiple connections because buggy servers do not use chunked transfer and therefore pipelining would be impacted. Thinking back I'm not sure if this was a general observation around the number connections Safari opens or it was implied that if a server uses chunked transfer that would solve the HOL issue around HTTP 1.1 Pipelining. If the latter I would appreciate specific pointers on how chunked transfer would solve the HOL issue in the case of HTTP Pipelining since the current text discusses this issue. BTW, does Safari 4.0 supports HTTP Pipelining? Thanks, Reinaldo=20