From owner-freebsd-arch@FreeBSD.ORG Wed Aug 17 08:46:30 2005 Return-Path: X-Original-To: freebsd-arch@freebsd.org Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 605A216A41F; Wed, 17 Aug 2005 08:46:30 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from digger1.defence.gov.au (digger1.defence.gov.au [203.5.217.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9076C43D45; Wed, 17 Aug 2005 08:46:28 +0000 (GMT) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: from ednmsw501.dsto.defence.gov.au (ednmsw501.dsto.defence.gov.au [131.185.2.150]) by digger1.defence.gov.au with ESMTP id j7H8iYRb025943; Wed, 17 Aug 2005 18:14:34 +0930 (CST) Received: from muttley.dsto.defence.gov.au (unverified) by ednmsw501.dsto.defence.gov.au (Content Technologies SMTPRS 4.3.17) with ESMTP id ; Wed, 17 Aug 2005 18:16:22 +0930 Received: from ednex501.dsto.defence.gov.au (ednex501.dsto.defence.gov.au [131.185.2.81]) by muttley.dsto.defence.gov.au (8.11.3/8.11.3) with ESMTP id j7H8iW015518; Wed, 17 Aug 2005 18:14:32 +0930 (CST) Received: from squash.dsto.defence.gov.au ([131.185.40.212]) by ednex501.dsto.defence.gov.au with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13) id QX6CR7K5; Wed, 17 Aug 2005 18:14:23 +0930 Received: from squash.dsto.defence.gov.au (localhost [127.0.0.1]) by squash.dsto.defence.gov.au (8.13.3/8.13.3) with ESMTP id j7H8jKFw027321; Wed, 17 Aug 2005 18:15:20 +0930 (CST) (envelope-from wilkinsa@squash.dsto.defence.gov.au) Received: (from wilkinsa@localhost) by squash.dsto.defence.gov.au (8.13.3/8.13.3/Submit) id j7H8jIPT027320; Wed, 17 Aug 2005 18:15:18 +0930 (CST) (envelope-from wilkinsa) Date: Wed, 17 Aug 2005 18:15:18 +0930 From: "Wilkinson, Alex" To: Colin Percival Message-ID: <20050817084518.GG25467@squash.dsto.defence.gov.au> Mail-Followup-To: Colin Percival , Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , freebsd-arch@freebsd.org References: <42F62C5F.6000609@freebsd.org> <20050807.101746.68985623.imp@bsdimp.com> <42F636BE.3020906@freebsd.org> <8664ub4bp3.fsf@xps.des.no> <42FCA675.7090300@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <42FCA675.7090300@freebsd.org> User-Agent: Mutt/1.5.9i Cc: Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= , freebsd-arch@freebsd.org Subject: Re: Adding portsnap to the base system X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Aug 2005 08:46:30 -0000 0n Fri, Aug 12, 2005 at 06:39:01AM -0700, Colin Percival wrote: >Dag-Erling Smørgrav wrote: >> Colin Percival writes: >>>Yes, pipelined HTTP. Basically, I spent six months on-and-off, and >>>at least two weeks of actual work, trying to fit pipelined HTTP into >>>fetch(3)... but the design of that library is all around the idea of >>>fetching a single file at once. In the end I gave up and wrote my >>>own code (phttpget) in under 24 hours. >> >> You are mistaken. Pipelined HTTP can be implemented in libfetch with >> the same ease (and the same limitations) as FTP connection caching, >> which was included from the start. > >Well, err... go ahead, then. I'm not going to tell the author of a >library that his library can't be modified to include a feature; all >I can do is point out that my best efforts were insufficient. > >I can see that it would be very easy to implement _persistent_ HTTP, >but implementing _pipelined_ HTTP is quite a different matter... erm ... what is meant by "_pipelined_ HTTP" ? - aW