Gnidrologist
July 5th, 2004, 02:58 PM
Isn't there any way to make winmx refresh the network connection every now and then by itself.
I had it with bloody connection timeouts. It's the worse flaw of winmx for me. I have a rare file in queue for 10 hours, I'm in a very low queues of 3-6 users and when It's getting much closer (10, 7, 3 in queue), all of them (or most) timeouts and I'm getting thrown in the end of the line...again Ret :devil
Usually retry does not help to get back on queue, it continues to timeout, but after I refresh the connection, all the users are back in queue instantly, which means that if a refreshing would be regular there would be a much lesser timeouts.
And also a strange fact. Timeout tends to occure exclusively when you're waiting in queue. It happens very rarely while transfering (both up and downloading). If I have queued file from a user it'll tiemout inevitabily after a while, but if i have transfer with the same user it can last uninterruptedly for meny hours.
I'm so pissed off. There are files that I try to get for a 6 months. Why connection timeout is such an issue with winmx. Other p2p networks has there own problems, but this is a major one on both, the wpn and oennap.
It would be nice if winmx would remember your place in queue for some time (say 10-20 min) after you get timeout or restart winmx. I suspect that something like that has been implemented in emule, because I had several occasions when after just restarting mule after short pause download restarted instantly on files that had only 5-10 sources. That would be imossible on winmx, wouldn't it?
I had it with bloody connection timeouts. It's the worse flaw of winmx for me. I have a rare file in queue for 10 hours, I'm in a very low queues of 3-6 users and when It's getting much closer (10, 7, 3 in queue), all of them (or most) timeouts and I'm getting thrown in the end of the line...again Ret :devil
Usually retry does not help to get back on queue, it continues to timeout, but after I refresh the connection, all the users are back in queue instantly, which means that if a refreshing would be regular there would be a much lesser timeouts.
And also a strange fact. Timeout tends to occure exclusively when you're waiting in queue. It happens very rarely while transfering (both up and downloading). If I have queued file from a user it'll tiemout inevitabily after a while, but if i have transfer with the same user it can last uninterruptedly for meny hours.
I'm so pissed off. There are files that I try to get for a 6 months. Why connection timeout is such an issue with winmx. Other p2p networks has there own problems, but this is a major one on both, the wpn and oennap.
It would be nice if winmx would remember your place in queue for some time (say 10-20 min) after you get timeout or restart winmx. I suspect that something like that has been implemented in emule, because I had several occasions when after just restarting mule after short pause download restarted instantly on files that had only 5-10 sources. That would be imossible on winmx, wouldn't it?