-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Tuesday 2006-12-19 at 01:15 -0500, Anthony Bryan wrote:
Here's the currently unimplemented idea for metalink, which could change if the clients find out it is clumsy or bad once they start putting it into practice.
For those unfamiliar, Linux Kernels (linux-22.214.171.124.tar.bz2) are signed with a separate file (linux-126.96.36.199.tar.bz2.sign) which looks like this:
This can be easily inside the Metalink, like this:
<verification> <signature type="pgp" file="linux-188.8.131.52.tar.bz2.sign"> -----BEGIN PGP SIGNATURE-----
That would be nice: if the file provider has signed it first, the metalink creator can include it. Otherwise, just sign the metalink file.
The "snag" is that checking both checksum and signature doubles checking time. I suppose that the user could select which one to use, same as rpm does, having both systems too, if I'm not mistaken.
Yes, there is currently no program that monitors the mirror servers and dynamically updates .metalink files according to mirror load.
I see this as being really useful at the busiest times, but maybe not as critical during normal times. But I might be wrong. I do think it would be really cool if someone was interested and would work on it tho.
I suppose that if the client sees that a server is serving slowly it can switch to a different one automatically and dynamically. After all, it is connected to several and it can compare. Perhaps having a central server recommending which servers to use, or modifying the metalink file dynamically would be even better, but I think it works as it is.
Anyway... a server listing current mirror speeds or load would also be useful to other people using plain ftp/http. It could be useful for selecting an update server for Yast/YOU, too.
Another problem is that each client should use minimum number of connections ie. servers to reach maximum download speed and than stop asking for more as each server has its maximum, so it will prevent others to download.
Yes, aria2 uses 15 connections to 15 different servers by default AFAIR.
But not several connections to the same server: that would be considered aggressive, I suppose. I don't think it does that, AFAIK, so that's good.
This can be changed with command line options. Or if a distribution shipped a binary, they could decide on a number they felt was better. I believe all the other clients go by whatever options the user has set, (I don't know the defaults off hand for all of them). It would be nice if clients could recognize they were downloading at the users maximum speed for their connection with 2 connections, so please don't open up 13 more.
I saw aria2c starting at 15, and later dropping to 4 or 5 automatically, maxing throughput. That's working well, I think.
It might be hard to fine tune what is most efficient. For dialup users, 1 is probably plenty. For me on cable, 4-6 is usually good in most conditions. I'd also like to find a number that is respectful to mirror server resources.
I suppose the client can tune automatically to use the minimum number that maxes speed.
- -- Cheers, Carlos E. R.
--------------------------------------------------------------------- To unsubscribe, e-mail: firstname.lastname@example.org For additional commands, e-mail: email@example.com