Good Morning, On Sat, Aug 22, 2009 at 04:06:01 +0200, Bram Neijt wrote: > > I would like to add that I don't think that the amount of software out > there already supporting this version is a large problem[1].
I would be careful with that - even if it is obviously wouldn't be a complicated change, it still requires somebody to be around to do that. And think of the users - they could simply run into errors when they try to use their metalink client. They won't know what's wrong and will conclude that metalinks don't work. They won't get a fancy message saying "your metalink client is a tad old! please go and look for an update". > I agree that we should ready ourselves for the future and I must admit > that I have not thought about the metalink format getting a revision or > second version. Although I agree we should ready ourselves, I think it > is still possible to call new version the "first and most-final-of-all" > versions. Yes, and I don't want to stop anything in any way. Just realize that openSUSE completely depends on the functionality now. There is no, no, no risk that I can take. (There are already enough ;) > There is the problem of the distribution at download.o.o, and I don't > want to endanger. Maybe it is possible to get the Aria2 to include a > version string in their user agent in the upcoming version? (currently > it's "aria2", maybe "aria2/version" would be good) A user agent string is of course sent. However, this brings you only so far. Experience shows two things: First, never use a user agent string for purposes other than informational. Second, there are always people out there who program things around the things that you do, which you are not aware of. This is a matter of probability. With a user base that goes into the millions, there is a high chance for the occurrence of many(!) applications that are tied to the technology that one released. They rely on something that you never guaranteed, but it's there and why not use it? > If you add the elements both inside and outside of the container, aria2c > will still run ok. I've tried this with putting URL elements outside of > the resources, and that worked just fine. That's good to know, thanks for the info, Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
pgp1bKTXYG8oT.pgp
Description: PGP signature
