On 12/09/2012 02:45 AM, Tim Rühsen wrote: > Am Samstag, 8. Dezember 2012 schrieb [email protected]: >> Hello >> >> I think wget should HTTP compression (Accept-Encoding: gzip, deflate). It >> would put less strain on servers being downloading from, and use less of >> their bandwidth. Is it okay to add this idea to the >> http://wget.addictivecode.org/FeatureSpecifications page? I don't know >> where on the page to add it, and thought I should check first before doing >> so in case there was a reason it isn't there >> >> Thank you for your time >> > > The next Wget to come (still called Mget) already has this feature working.
I don't think there's been agreement that the next Wget will be called Mget, or that the current work on Mget represents a step towards replacing Wget, so I think it's quite misleading to refer to Mget as "the next Wget to come". Current Wget sources already have concurrent downloading available, and many other features, both new and pre-existing, that are not featured in Mget. Wget proper doesn't have gzip/deflate support currently, but it's not too hard to add it, and I wouldn't be surprised if it gets added in the near future; it just hasn't been as high a priority as other recently-introduced features had been, I believe. -mjc
