Since you're behind a firwall you can only make outgoing connections to ther hosts but yet it doesnt prevent you from communicating with them even though you're behind one. You can make connections to other hosts (outgoing to you) but other hosts cant make connections to you (incoming to you) b/c the firewall blocks them. With the gnutella protocol since you're behind a firewall when some tries downloading something from you they must request a PUSH. a PUSH is a packet telling you (the person behind the firewall) that another host wants a file and you'll have to make a connection to that host and upload the file. Instead of the usually that host connecting to you and downloading a file.

Yes it would, then we wouldnt have people forcing their IP ADDRESSES to 255.255.255.255 or some other invalid ip address. When I say automatic forced ip, I mean you would simply click the "FORCE IP ADDRESS" checkbox and it would do some type of DNS query and find your true ip address. It would be the same as if you entered it in yourself.

If you read what I wrote...

have some kind of checksum for search entries (people are searching for incomplete files ex: N1-2506752-The Band - The Song.mp3 which is causing congestion). People actually think that it is the filename associate with that file. I'm assuming you have some type of "order check" because all incomplete/downloading files have a different prefix to the filename. In shorter words something to stop people from searching and sharing incomplete files as with the prefix you assign.

If you ever looked in your monitor window while using LimeWire you can see queries that consist what I'm speaking of.

ex:

If you use LimeWire and start a download. LimeWire will place the file in the designated INCOMPLETE folder. Say you're downloading the file band - song.mp3. Now if you looked back in your INCOMPLETE folder you would say a file with the filename N1-2503145-band - song.mp3. But when the file has finished downloading it copies it to your SHARED folder with the correct name band - song.mp3. I'm assuming the N1-2503145 while you're downloading a file is a prefix LimeWire uses so if that download drops and it picks up another it would not write over the file or mess up the new download for whatever reason. Like I said above if you watch your monitor window for a minute you actually see queries for N1-12543521-other band - another song.mp3. Which means people actually think when they first downloaded that file other band - another song.mp3 it was really N1-12543521-other band - another song.mp3. So they search for this file further congesting the network with unnecessary traffic. The thing I was speaking of was when a person using LimeWire (b/c only LimeWire uses prefixes to incomplete/partial downloads) and they try searching for N1-12543521-other band - another song.mp3 it would perform some type of checksum (it checks the sum (entry)) to prevent hosts from searching for files that are not out there (unnecessary traffic).

One last thing who said anything about a database anywhere!?




Do not come here bitching b/c you cant download or find files. Whos fault is it b/c you cant find episodes of evangelion? No ones so stop whining. The network consists and is ran by the users.


We are the only ones who can keep it alive.