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 Message-ID: <041d01c1791c$883822b0$0200a8c0@lifelesswks> From: "Robert Collins" To: "Roth, Kevin P." , "cygwin-apps mail-list \(E-mail\)" References: <6EB31774D39507408D04392F40A10B2BACC7DC AT FDYEXC202 DOT mgroupnet DOT com> Subject: Re: [setup.exe] HTTP v1.1 and persistent connections Date: Fri, 30 Nov 2001 08:24:04 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 29 Nov 2001 21:28:01.0722 (UTC) FILETIME=[B941B1A0:01C1791C] It's not too late at all. In fact I think we've already discussed this in the context of resumable downloads ;]. At this point however, the key is getting the internal IO consistent. Later on we can wrap classes around libhsync/libcurl. If someone wants to do this now, I'm cool with that too. Rob ----- Original Message ----- From: "Roth, Kevin P." To: "cygwin-apps mail-list (E-mail)" Sent: Friday, November 30, 2001 8:23 AM Subject: RE: [setup.exe] HTTP v1.1 and persistent connections 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