Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [setup.exe] HTTP v1.1 and persistent connections Date: Thu, 29 Nov 2001 16:23:23 -0500 Message-ID: <6EB31774D39507408D04392F40A10B2BACC7DC@FDYEXC202.mgroupnet.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [setup.exe] HTTP v1.1 and persistent connections Thread-Index: AcF5GA0t7GHxs2feREevbkus6suY2gAA3eFw From: "Roth, Kevin P." To: "cygwin-apps mail-list (E-mail)" X-OriginalArrivalTime: 29 Nov 2001 21:23:24.0422 (UTC) FILETIME=[13F91260:01C1791C] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id fATLNWi24686 I don't know whether it's too late at this point in the game to mention this, but libcurl already supports all the things you've mentioned (full http/1.1 support, reusable connections, etc) and it's licensing makes it fairly easy to include into your code or staticly link if you need to avoid run-time dependancies. And it compiles nicely for native Win32 using minGW, so you don't have to link against cygwin1.dll for any reason... --Kevin -----Original Message----- From: Robert Collins [mailto:robert DOT collins AT itdomain DOT com DOT au] Subject: Re: [setup.exe] HTTP v1.1 and persistent connections > Have in mind that for each package to be downloaded a > new connection is made, so the keep-alive feature does > not make too much sense, but the slowdown I'm talking > about is significant. I hope this will decrease the > overall processing time. What the HTTP object could do is have a connection pool maintained in a static member, and new downloads can reuse connections from that pool if they are still open. Rob