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." <[EMAIL PROTECTED]> To: "cygwin-apps mail-list (E-mail)" <[EMAIL PROTECTED]> 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:[EMAIL PROTECTED]] 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
