As my user name says...
Posted: Sun Dec 06, 2009 11:16 pm
...I'm curious.
I run Azureus. Today I encountered someone in a swarm I was involved with, running your client...(v. 1.76) I was pounding out bandwith to said client (in excess of 50KB/s [Azureus: KBytes:not bits]) for at least ten minutes and it seemed that the client was constantly switching from one piece to the next, to the next, to the next...without completing anything. Is this the way this program is designed to work? Keeping 50+ piece files open at one time? When I booted him off my "gravy train" (so I could upload to those I was DLing from)...he still had 0% complete pieces. Seems like a rather bizarre way to approach file SHARING...Leeches Suck.
Is this due to the way he has configured the client or is this the "out of the box" modus operandi?
Call me "Curious"
I run Azureus. Today I encountered someone in a swarm I was involved with, running your client...(v. 1.76) I was pounding out bandwith to said client (in excess of 50KB/s [Azureus: KBytes:not bits]) for at least ten minutes and it seemed that the client was constantly switching from one piece to the next, to the next, to the next...without completing anything. Is this the way this program is designed to work? Keeping 50+ piece files open at one time? When I booted him off my "gravy train" (so I could upload to those I was DLing from)...he still had 0% complete pieces. Seems like a rather bizarre way to approach file SHARING...Leeches Suck.
Is this due to the way he has configured the client or is this the "out of the box" modus operandi?
Call me "Curious"
