JimmySask
join:2004-06-24
Regina, SK
| reply to DB7654321
Re: first
The other problem with using BT to to distribute (although only if it is integrated to the update process) is the very nature of BT. It is a "tit for tat" filesharing system, which requires you to upload in order to download. Anyone remember Kazaa? I can already imagine the number of people getting upset that MS is "stealing" their bandwidth, even if it is in a licensing agreement, just because that's the way people are. This is especially true when you factor in the lovely bitcaps some providers have, and large downloads like SP2. Allowing people to use it freely would be cool, but MS would have to keep a careful distance from it because anyone can post a torrent file, based on what they want to call it, as opposed to the actual contents of the file. |
|
Goldengamego
Premium
join:2004-02-22
Okemos, MI
1 edit | The protocol is open and the code is available for modification (the license allows you to modify without releasing the modified source), it could be redone so the .torrent is passed to BITS/AU without any user interaction or just remove .torrents entirely.
BT is very different from that Kazaa crap, if enough seeds available you don't have to upload. Microsoft could config it so that only BB users will use BT (that would still save lots). With BT you only upload while you are downloading, after that Windows would install the update and delete the file.
Also don't bring up the whole corprate/school/goverment networks are behind a firewall thing, they use SUS to get their updates.
--
Because Goldengamegod won't fit:p |
|
