ubergeeknz:markl:ubergeeknz:]
This is all very well. But most users would not have a *clue* to do this or even that it would be an issue. ISPs should probably brace for a whole lot of customers with overage in the near future.
I understand why Microsoft have done this, it's a smart move and one I've long wanted to see in Enterprise update distribution at least, but not telling people that you will be using their bandwidth to allow other customers to download updates is a bit on the nose.
I disagree. Like I said earlier, I doubt that must Windows updates are large enough over a month to cause caps to be blown. Obviously there are exceptions to that, of course, but I can't see there being a massive deluge of people with this problem ask calling their isp to find out why they've gone over their cap
It's the principle of it, for me. Also no matter how small the update, if your system reseeds it (for want of a better term) 100x or 1000x, or say there are errors and it is re-downloaded infinitely, it will add up.
I don't know, but I'm assuming that it works in a similar manner to bittorrent - that is, you "seed" files but in actual fact because each file is shared in "chunks", that really only means that any "chunks" you've downloaded already are available for sharing to others - so in all probability, with millions of people also sharing the same downloads, you'd almost never seed an entire update yourself...
Having said that, a real plus as an extra, if anyone from Microsoft is reading (LOL), would be to give us visibility and fine grained control over this behaviour - so we can see how many "chunks" each update is made up of, and what size, how much from each that we've seeded, perhaps allow us to seed for a certain time then stop, etc.
There are a LOT of options with this...