ISO downloads with multiple mirrors for higher reliabilty, automatic checksum verification

[Dimitar Vasilev]

>
>
> Can you think of some per transfer and per server options that would help
> the situation?
>
> Maybe something like for each transfer max connections and max servers and
> for servers something like max connections and segment size?
>
> (( Anthony Bryan
> )) Metalink [ http://www.metalinker.org ]
>
> _______________________________________________
> freebsd-hubs at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hubs
> To unsubscribe, send any mail to "freebsd-hubs-unsubscribe at freebsd.org"



Hello!
Brief addition of mine to the idea above. Haven't went though metalink
implementation deeply.

Could it be like a txt file on server, which clients can fetch and obey like
robots.txt
E.g - metalink.txt in pub/FreeBSD directory

Sample
------------------------------
maxconn=3 (max connections per client)
ssize=1024(bytes,kbytes,megs,gigs - your pick, but should be equal for all
machines)
maxclients=50
------------------------------

and some central db/rss feed on metalink site db that parses these files and
instructs clients that server has reached maximum capacity and they should
move to another machine?
In similar manner, condition of freebsd mirror sites is checked via mirmon -
file pub/FreeBSD/TIMESTAMP and later a robot crawls to check it and reports
on web page.
Happy evening and a nice week!
-- 
Димитър Василев
Dimitar Vassilev

GnuPG key ID: 0x4B8DB525
Keyserver: pgp.mit.edu
Key fingerprint: D88A 3B92 DED5 917E 341E D62F 8C51 5FC4 4B8D B525