-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hrvoje Niksic wrote: > Micah Cowan <[EMAIL PROTECTED]> writes: > >>> It just occurred to me that this change breaks backward compatibility. >>> It will break scripts that try to clean up after Wget or that in any >>> way depend on the current naming scheme. >> It may. I am not going to commit to never ever changing the current >> naming scheme. > > Agreed, but there should be a very good reason for changing it, and > the change should be a clear improvement.
How do those reasons differ? :) > In my view, neither is the > case here. It seems like a fairly clear improvement to me; at least, I believe that the improvement would outweigh the rather mild risk that it might break something. It's a mild improvement, but it's an even milder risk, AFAICT. > For example, the change to respect the Content-Disposition > header constitutes a good reason[1]. (I don't seem to have the footnote you seem to have intended to put there.) I'm not sure how good an example Content-Disposition is, though, given that the risk of backwards-incompatibility is probably virtually nil. In that this is a more general change, whereas that is a specific change (to a certain subset of URLs). Of course, your opinion is important to me, and to be honest, I didn't expect to find any resistance to this idea (there were no comments besides mine on the original post back in July). So I welcome further feedback. However, at the moment, I don't see any compelling reason not to apply the change, and do find reason to apply it (interoperability seems like a desirable trait). Hm... wget-patches seems not to be archived... There's a supposed link to a gmane archive, but it's apparently empty. :\ That makes it difficult to refer to the original post from July 13. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHLuyC7M8hyUobTrERCJ1lAJ99AfiCPkjPra9UlBakgyKlUMhyFQCfY0ht 57y31BM4+6YFadFnhkVH62Q= =UQ5g -----END PGP SIGNATURE-----
