Upload queue, host-limit algorithm aborts uploads
Posted: 20 Aug 2013 21:43Scenario:
1) Shareaza 2.6.00 x64 on Windows 7 x64
2) Upload queue setting: Limit per unique host = 2
3) A user wants 3 of my files.
4) Every few minutes, his client makes a request for an incomplete one, one that is not already in my queues; typical host behavior, I think.
5) The host has 2 entries in a upload queue, one is actively uploading the other may be uploading or waiting.
Observation:
When the host requests a 3rd file, Shareaza aborts the first actively-uploading file, and appends the new 3rd file to the queue.
The next upload doesn't get very far when the next request comes in and aborts that upload! More time is spent re-connecting than uploading data.
If I were the host, I would expect my newest request to be rejected instead of making it abort the upload that is in progress. Is this the way Shareaza is supposed to work? In order for the upload to complete normally, the host would have to stop requesting when they had 2 entries in my queue.
Just asking.
1) Shareaza 2.6.00 x64 on Windows 7 x64
2) Upload queue setting: Limit per unique host = 2
3) A user wants 3 of my files.
4) Every few minutes, his client makes a request for an incomplete one, one that is not already in my queues; typical host behavior, I think.
5) The host has 2 entries in a upload queue, one is actively uploading the other may be uploading or waiting.
Observation:
When the host requests a 3rd file, Shareaza aborts the first actively-uploading file, and appends the new 3rd file to the queue.
The next upload doesn't get very far when the next request comes in and aborts that upload! More time is spent re-connecting than uploading data.
If I were the host, I would expect my newest request to be rejected instead of making it abort the upload that is in progress. Is this the way Shareaza is supposed to work? In order for the upload to complete normally, the host would have to stop requesting when they had 2 entries in my queue.
Just asking.