Quote:
Originally posted by ssj4_android
Why does browsing take up server bandwidth on WPNP? The WinMX 3 one. Doesn't it connect to the other person to get the list?
|
It is just my educated guess that supernodes serve the browse requests for the very same reason why they handle the search requests - efficiency. Imagine a 56 k dialup with 10.000+ shared songs (and I know there are users like this!). Such library contents may correspond to about 1 MB of index data (you can get a good idea by checking the size of your library.dat file and comparing it to the number of files you are sharing). Assuming an optimistic 30 kbit/s upstream speed it takes about 5 minutes from the poor dial-up to push this chunk of data to its supernode. As such a big shared library will collect a lot of search hits and consequent browse requests it is obvious that the dial-up would be totally choked in serving browse requests alone unless the faster supernode would not handle the job on its behalf.
- tg