"Patrick Sullivan" <> wrote in message
news:BvKdnfbGP9zYlh_fRVn-...
>> You just don't get it !
>> Load Balancing has nothing to do with YOUR PC. It has to do with a
> distribution service
>> (FTP or HTTP).
>
> There's the SETI effort, distributed computing to solve a problem, and
> there
> are others. There is also p2p filesharing like Napster used to do, and
> Kazaa
> and some others are still doing. I was distributing something over a
> connection that should have been quiet, that is why I said I was
> acting like
> a server for akamai. I figured at best, it was something like SETI or
> Kazaaa.
>
>> Think about it....
>> How do you allow millions of customers (clients) to download
>> MegaBytes of
> data ? By Load Balancing the servers through a 3rd party hosting
> company
> such as Akamai Tech.
>
> Because MS is too lazy or poor to do that themselves?
>
>> It isn't going to be in the Registry. Akamai isn't software residing
>> on
> your computer. It
>> is Domain Name resolution redirection to the load-balanced site.
>
> Ok, ok, I understand that. You guys just do not understand what I was
> complaining about, evidently. Megabytes of data were being exchanged
> with no
> update services active.
>
>> For example;
>> ping -a www.trendmicro.com
>>
>> Pinging a151.g.akamai.net [130.81.64.50] with 32 bytes of data:
>>
>> Reply from 130.81.64.50: bytes=32 time=12ms TTL=58
>> Reply from 130.81.64.50: bytes=32 time=12ms TTL=58
>> Reply from 130.81.64.50: bytes=32 time=13ms TTL=58
>> Reply from 130.81.64.50: bytes=32 time=13ms TTL=58
>>
>> Ping statistics for 130.81.64.50:
>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> Approximate round trip times in milli-seconds:
>> Minimum = 12ms, Maximum = 13ms, Average = 12ms
>>
>> Notice that although I requested a PING on the Domain
>> "trendmicro.com", it
> returned a host
>> at the Domain "akamai.net".
>>
>> It is that simple.
"Act as server" means you must be *sending* OUTBOUND packets for file
transfer. Windows Update (from Akamai) using INBOUND packets to *get*
files. There is always some outbound packets sent for the inbound
packets for downloading a file but that traffic is small and used for
acknowledgements. You are *downloading* the updates (from Akamai)
similar to when you download files from a web site for drivers,
applications, utilities, or documents. You downloading files does NOT
make you a server. You are also, in no way, part of the load-balanced
server network provided for the download. You are the client, not the
server. Kazaa, BitTorrent, or other P2P schemes have nothing to do with
Windows Update and Akamai. You are NOT redistributing any of the files
that you receive.
Note that you never did mention in your posts whether the bandwidth
hogging communications were inbound or outbound. The assumption was
made that if it was to Akamai that it was most likely to be for Windows
Updates and that would be for INBOUND traffic. You are the client
receiving a file download for a Windows update that Microsoft is using
Akamai to distribute to their worldwide customer base.
--
__________________________________________________ __________
** Post your replies to the newsgroup - Share with others **
For e-mail Reply: remove "DELETE", add "~VN56~" to Subject.
__________________________________________________ __________