| |||||||||||||
|
| |||||||||||||
How to fix itHow to fix itPosted Jul 14, 2008 17:45 UTC (Mon) by i3839 (subscriber, #31386)In reply to: How to fix it by epa Parent article: Study: Attacks on package managers
Considering the current topology of the Internet mirrors will stay making sense and be more efficient than peer-to-peer systems. Throw in the huge differense between clients' upload and download bandwidth and mirrors make even more sense. Better to experiment with multicast...
(Log in to post comments)
How to fix it Posted Jul 15, 2008 15:30 UTC (Tue) by salimma (subscriber, #34460) [Link] Multicast would be useful for a sysadmin wanting to update multiple computers all at once, but otherwise, data still has to be transmitted multiple times.
How to fix it Posted Jul 17, 2008 14:41 UTC (Thu) by i3839 (subscriber, #31386) [Link] I was more thinking about distro's multicasting package updates and everyone being able to pick them up. Sending a package update ten times a day for ten days means almost everyone has the chance to pick it up. Uploading a file a hundred times instead of once per user uses much less bandwidth if you've more than a few hundred users. Bandwidth usage can be controlled on the client side by choosing how many streams are read simultaneously. Throw in a traditional client-server thing to retrieve lost packets or missed updates, and to enable people with crappy ISPs or routers which don't support multicast, and you've a complete solution. Of course multicast has its downsides and troubles, so you'd want to use Source Specific Multicast, and IGMPv3 support is needed for that. No idea how well (home/ISP) routers do that though.
|
|
||||||||||||