When you are already downloading something, can someone make it so you can add more users. Or be able to close the download click on a new user and have it continue from the saved file?

I think I know what you're saying. I had to read it a couple of times and I am guessing.

Are you saying: You would like to be able to stop downloading from a particular host (like when the speed is incredibly slow or gets stuck at 0 kb/s) and try to get it from a new host without killing the download?

I'd like to see that too. Instead of trying to do a new search. Sometimes they don't come up again for a long time. I'd like the ability to stop the download from one user and keep it in my download queue. Sometimes files will start to download without showing up in a result.

Or better yet, if more users would check their upload monitor now and then and kill the 0 kb uploads. Sometimes it can kick back in and start again at a reasonable speed. But if we kill it on our end, we have to search (and find it) again.

When they get stuck at 0 kb/s?? Why?

I've looked at my Monitor and seen all uploads sitting at 0. If I kill them, I see them log back on (or new one's) and they start back up again. Actually uploading.

I hate to sit and stare at my download going at a whopping speed of 0kb/s. (no, I don't literally sit there and stare at it! ) I would prefer if the other user would kill the upload. Let me try it again or find another host without re-searching.

Please, please, please explain to me how it hurts the network...

It would seem to me that letting them sit at 0 would hurt the network. Others can't download from me if my upload slots are filled up with non-uploading users.

(I'm certainly not trying to sound nasty, if that's how this comes across. I'm genuinely interested. I don't fully understand the workings of Gnutella and what hurts it / helps it.)

uploads shouldn't be sitting at 0kb/s in 2.6.3. are they?

Not so far. I just upgraded the other day. My downloads still get stuck at 0kb/s, though. Maybe it's due to downloading from someone with an older version.

But, I'm still curious about what helps/hurts the network.

bpmax, read a little closer.

julie said uploads weren't getting stuck, downloads were.

and killing uploads doesn't hurt the 'network' -- it just annoys the person trying to get the file.

Like I've said regarding killing other's uploads: I've seen them come right back and then actually upload at a decent speed.

Why would they want their file sitting at 0? That's when it's a problem. They're not getting the file they want and can't get it from someone else if it's stuck in my upload queue at 0.

I honestly wish someone would do that for me. Because sometimes a new search won't come up with a new result. If they kill the upload, then I can try again with them.

When my downloads get stuck at 0 kb, it's not just a temporary situation (well, very rarely). It usually (99% of the time) gets stuck until I quit the program.

Besides the "requery", it's the most annoying thing to me about LimeWire. But, since I am a Mac user, I don't have much choice about which program I can use. I can't use multiple p2p's as others can.