On Tuesday 12 June 2007 14:34:05 Brent wrote: > I think one really great way to help with this problem is if there was a > way to have the mirrors run torrent seeds too. That's what the rel-eng team decided to investigate, with getting support into mirrormanager hopefully so that it Just Happens. > If that were to happen > then the local network mirrors thing would pretty much automagically > work itself out. If the people in the LAN know about the FTP/HTTP > mirror they use it, if they don't most of the good Bittorrent software > tries hard to find local nodes to connect to. So torrent users would > still get it using the LAN _mostly_ and the mirrors would also be > helping to seed the torrents during the slow beginning part. Meh, most bittorrent stuff I've seen isn't that great about using "local" connections, unless it's right on the same network. Most mirrors are likely not on the same network as the client machines, your public facing network is rarely your private network too. > It does mean that mirrors might have more bandwidth being used on their > external links, but if they are a mirror they are probably ok with that > bandwidth being used. I don't see why they would care if it is with > HTTP, FTP, or torrent. Right, many complain that not all their bandwidth is being used due to resource contention for http or whatnot. Having more methods for them to use the bandwidth and flex their muscles are better (: > Also the more mirrors you have using it the more > feasible it becomes to start looking at the possibility of maybe doing > updates via the torrent network or something like that. Things like > that make the mirror lists start to become obsolete. The majority of the update files are too small for bittorrent to really be worth while. -- Jesse Keating Release Engineer: Fedora
Attachment:
pgpA3OXQk3Y5l.pgp
Description: PGP signature
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
