News for hackers. Stuff that matters.

A comment on Curl vs. Wget.

Re:Curl vs. Wget by contingencies on Wednesday March 02, 2016 @06:52PM (#11214059)
If nobody's tried it, axel mentioned in the report as possibly abandoned has the awesome feature of splitting a download in to parts and then establishing that many concurrent TCP connections. Very useful on individual TCP flow rate-limited networks.
[ Parent | on HN ]
Re:Curl vs. Wget by icebraining on Wednesday March 02, 2016 @07:52PM (#11214305)
Axel is great, but nowadays I reach for aria2 instead, which can do the same, but also supports bittorrent and (s)ftp.
[ Parent | on HN ]
Re:Curl vs. Wget by hcarvalhoalves on Wednesday March 02, 2016 @07:06PM (#11214106)
Haven't found anything better than axel to saturate the link yet.
[ Parent | on HN ]
Re:Curl vs. Wget by MoSal on Wednesday March 02, 2016 @08:13PM (#11214372)
Try saldl[1]. It depends on libcurl. So protocol support should be good and reliable.

[1] https://github.com/saldl/saldl

[ Parent | on HN ]
Re:Curl vs. Wget by contingencies on Wednesday March 02, 2016 @09:53PM (#11214736)
https://github.com/saldl/saldl/wiki/saldl_vs._aria2
[ Parent | on HN ]
Re:Curl vs. Wget by MoSal on Thursday March 03, 2016 @07:18AM (#11216360)
FWIW, this page is incomplete and outdated.

For example, `--mirror-url` was implemented. So, it is now possible to download from two sources concurrently.

[ Parent | on HN ]