On Mon, Dec 15, 2008 at 6:05 PM, Nicolas Alvarez <[email protected]> wrote: > > Anthony Bryan wrote: >> This is a neat patch, but IMHO it doesn't belong in the curl command line >> client. It adds functionality that goes well beyond what curl is designed >> for and the UNIX philosophy behind it: to do one thing and do it well, >> which is to transfer individual URLs from/to individual sites >> and to allow all manner of tweaking that behaviour. That's why it >> doesn't do HTML parsing, remote URL globbing, recursive transfers, >> PAC proxy configuration, etc. >> >> Metalink support is designed for something other than what curl's primary >> mission is about. An indication of this is that of curl's 128 options, >> half become irrelevant (and even more are marginally relevant) when doing >> Metalink transfers. Adding two additional library dependencies to curl >> is also an issue. > > Can I say "I told you so" or will I get flamed?
no flames :) it's kinda confusing when Daniel, curl author, writes "The Metalink guys host a list of project ideas and one of those ideas is to add metalink support to curl, and I recently bumped the stakes a bit by raising the bounty with an additional 200 USD so that the offer is now 500 USD for the person or team that brings the feature as described. My primary motivation for doing this is that I like the metalink idea and I'd like to help making sure it gets used more widely." http://daniel.haxx.se/blog/2008/11/09/metalink-in-curl-bounty/ -- (( Anthony Bryan ... Metalink [ http://www.metalinker.org ] )) Easier, More Reliable, Self Healing Downloads --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Metalink Discussion" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/metalink-discussion?hl=en -~----------~----~----~----~------~----~------~--~---
