{"thread":{"id":"39174","subject":"curl","startedAt":"2015-04-28T02:49:51Z","lastAt":"2015-04-28T09:27:13Z","messageCount":3,"participants":["Thiago Farina","Jeff King","Carlos Martín Nieto"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"260091","messageId":"CACnwZYc8VvQ4mh3pbVcd06uc6YZOXnrGOEpTu19qacBy8v_Y8A@mail.gmail.com","threadId":"39174","inReplyTo":null,"subject":"curl","fromName":"Thiago Farina","fromEmail":"tfransosi@gmail.com","sentAt":"2015-04-28T02:49:51Z","receivedAt":"2015-04-28T02:49:51Z","isPatch":false,"sender":{"key":"tfransosi@gmail.com","avatar":"https://avatars.githubusercontent.com/u/970071?v=4"},"body":"Hi,\n\nIs it right that git uses libcurl to download while libgit2 does without it?\n\n-- \nThiago Farina\n"},{"id":"260095","messageId":"20150428045732.GD24580@peff.net","threadId":"39174","inReplyTo":"CACnwZYc8VvQ4mh3pbVcd06uc6YZOXnrGOEpTu19qacBy8v_Y8A@mail.gmail.com","subject":"Re: curl","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2015-04-28T04:57:32Z","receivedAt":"2015-04-28T04:57:32Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Apr 27, 2015 at 11:49:51PM -0300, Thiago Farina wrote:\n\n> Is it right that git uses libcurl to download while libgit2 does without it?\n\nI'm not sure if you mean \"right\" as in \"this statement is true\" or as in\n\"is this a good thing that it is the case\".\n\nFor the former, yes, libgit2 does not use curl.  On Windows, it can use\nthe native http calls (which do nice things like using the system proxy\nand auth systems). On Unix, I think it is a combination of hand-rolled\ncode, openssl, and an imported http parser (from nginx).\n\nWhether that is a good idea or not, I can't comment too much. From what\nI have seen discussed in libgit2 issues, the stock http transport is\nmeant to be bare-bones (but with minimal dependencies). But it could\nco-exist with a curl transport (just as it does with the WinHTTP\ntransport).  Maybe Carlos (cc'd) can say more.\n\n-Peff\n"},{"id":"260120","messageId":"1430213233.2098.13.camel@elego.de","threadId":"39174","inReplyTo":"20150428045732.GD24580@peff.net","subject":"Re: curl","fromName":"Carlos Martín Nieto","fromEmail":"cmn@elego.de","sentAt":"2015-04-28T09:27:13Z","receivedAt":"2015-04-28T09:27:13Z","isPatch":false,"sender":{"key":"cmn@elego.de","avatar":"https://avatars.githubusercontent.com/u/335443?v=4"},"body":"On Tue, 2015-04-28 at 00:57 -0400, Jeff King wrote:\n> On Mon, Apr 27, 2015 at 11:49:51PM -0300, Thiago Farina wrote:\n> \n> > Is it right that git uses libcurl to download while libgit2 does without it?\n> \n> I'm not sure if you mean \"right\" as in \"this statement is true\" or as in\n> \"is this a good thing that it is the case\".\n> \n> For the former, yes, libgit2 does not use curl.  On Windows, it can use\n> the native http calls (which do nice things like using the system proxy\n> and auth systems). On Unix, I think it is a combination of hand-rolled\n> code, openssl, and an imported http parser (from nginx).\n> \n> Whether that is a good idea or not, I can't comment too much. From what\n> I have seen discussed in libgit2 issues, the stock http transport is\n> meant to be bare-bones (but with minimal dependencies). But it could\n> co-exist with a curl transport (just as it does with the WinHTTP\n> transport).  Maybe Carlos (cc'd) can say more.\n\nThis is accurate, though I'll add that the development version of\nlibgit2 now uses SecureTransport instead of OpenSSL on Mac OS X.\n\nBut this is just the default. You can replace what libgit2 will use as a\ntransport if you have special needs. Visual Studio use their own network\ncode, and the cargo package manager uses libcurl. Eventually libcurl\nsupport will likely be added to mainline libgit2, when we find time.\n\n   cmn\n"}]}