we do not need 'swarmed downloads', do you understand the word swarmed? Gnutella developers are researching ways to avoid/reduce broadcast traffic (which is the number one cause of the network being so slow at the moment). Broadcast traffic takes up ~50% of your bandwidth which means that other half is divided up for downloading and uploading. Xolox or whatever is hurting the gnutella network, Vinnie even said so himself.

http://www.bearshare.net/forum/showt...?threadid=4872

it produces "machine generated queries: which wastes bandwidth b/c those queries are not efficent in matching enough files other hosts have.

Xolox is bad for the network. Load up LimeWire and look in the Monitor window and look how many

Band - Song 01.mp3 type of queries you get. How many people are going to have that file in that exact filename. They may of named it a little different so that query just wasted bandwidth. It would me efficent to such just for that song name or band name and filter the results with a set of rules.

We DO need swarmed downloads. Just with better implementation. If the GDF could get its act together an implement file hashing we could really get things moving. They need to just make a move and get it done! Same goes for meta data.

Limewire should also introduce some type of reflector technology (defender). This would help lower badwith as well.

Hi!

I just wanted to point out, that AFAIK Xolox doesn't search for the whole filename (these searches have been around long time before Xolox), but it "just" repeats the original search. That's just the way I did it manually with LimeWire before, since that's the only way to find enough hosts with the file I'm looking for.

Robin

Look you must get rid of unwanted broadcast traffic first then they can focus on download succession rate.

Why dont you stop [inapropriate language deleted] about something that is for free. If you want to do it so bad then you make a gnutella client and release it. There are a lot gnutella client sources out there.

router.limewire.com is a "reflector". Reflectors are made for high bandwidth hosts (cable/dsl, T1s, etc).

Also read my post on

http://www.gnutellaforums.com/showth...=696#post10251

That should explain my point in a little more detail

I am [inapropriate language deleted] about the GDF which is slowing implementation of much needed features. Even if I wrote a gnutella client with these features it would not be supported by the general network until the GDF got its act together.


Hmm, someone else correct me if I am wrong but router.limewire.com is a host catch isnt it, not a reflector. A reflector is a gnutella client users can connect to the gnutella network through. They would stay connected and all searches would be sent to the network through the reflector client and all of their available uploads would be listed on the reflector and the reflector would return their hits for them so that they do not actually interact directly with the network.

And yes, we still need swarmed downloads!! JUst look at the popularity of xolox and it is still very unpolished and brand new.

GDF, get the file hashes, the metadata and the swarmed downloads worked out.

Ok, BearShare now offers bitrates for MP3s. Will LW be supporting this in 1.8? How about other meta data? SHA1 file hashes?