{"thread":{"id":"16111","subject":"large publicly accessible HTTP archive?","startedAt":"2008-10-31T17:07:01Z","lastAt":"2008-10-31T19:01:53Z","messageCount":2,"participants":["Bryan Larsen","Daniel Stenberg"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"94425","messageId":"490B3B35.60508@larsen.st","threadId":"16111","inReplyTo":"S1751776AbYJaQ5O/20081031165714Z+111@vger.kernel.org","subject":"large publicly accessible HTTP archive?","fromName":"Bryan Larsen","fromEmail":"bryan@larsen.st","sentAt":"2008-10-31T17:07:01Z","receivedAt":"2008-10-31T17:07:01Z","isPatch":false,"sender":{"key":"bryan@larsen.st","avatar":"https://avatars.githubusercontent.com/u/32073?v=4"},"body":"Hello,\n\nI'm one of the maintainers of MacPorts git port.\n\nA long time ago, we had problems pulling extremely large archives over \nHTTP on PowerPC machines.  By large, I mean on the order of 500 \nmegabytes: I was testing using an embedded Linux distribution.\n\nWe \"fixed\" the problem by turning off CURL_MULTI and ignored the \nproblem.  Yes, bad form, I know.\n\nOur problems were against curl 7.16.2.\n\nHowever, in recent git's, CURL_MULTI is required to do an HTTP push, so \nwe've had users complaining.\n\nCurl is up to 7.19.0, they may have fixed our problem.  Unfortunately, \nthe distribution I used for testing is gone now.  Putting up a local \narchive doesn't exhibit the problem either.\n\nIs anybody aware of a very large HTTP accessible repository that \nwouldn't mind me doing a few test pulls from?  By large, I mean >500 \nmegabytes of network traffic for a single pull.\n\nthanks,\nBryan\n"},{"id":"94439","messageId":"alpine.LRH.1.10.0810311959330.17280@yvahk3.pbagnpgbe.fr","threadId":"16111","inReplyTo":"490B3B35.60508@larsen.st","subject":"Re: large publicly accessible HTTP archive?","fromName":"Daniel Stenberg","fromEmail":"daniel@haxx.se","sentAt":"2008-10-31T19:01:53Z","receivedAt":"2008-10-31T19:01:53Z","isPatch":false,"sender":{"key":"daniel@haxx.se","avatar":"https://gravatar.com/avatar/69fdca87edd17cee21ca2e79fc2ff671d644603c3dc27167430f3cd3dbab7ba8?d=mp&s=160"},"body":"On Fri, 31 Oct 2008, Bryan Larsen wrote:\n\n> We \"fixed\" the problem by turning off CURL_MULTI and ignored the problem. \n>\n> Our problems were against curl 7.16.2.\n\nRight, libcurl has had 8 releases since with perhaps an average of 30 bugfixes \nper release so...\n\nI'm not aware of any current known libcurl bugs with the multi interface and \n\"simple\" HTTP transfers such as this.\n\n-- \n\n  / daniel.haxx.se - libcurl hacker\n"}]}