Disconnect slow user will not calculate multislots

Bug #1406352 reported by Sopor
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AirDC++
New
Undecided
Unassigned

Bug Description

If i use multislot downloads and the speed is 2 MiB/s, but i use 5 slots at 400 KiB/s and i have set the 'Disconnect user' to 600 KiB/s, it seems that it will disconnect me from this user. It will not calculate the total speed, instead it only see each download slot.

Revision history for this message
Sopor (sopor) wrote :
Revision history for this message
Sopor (sopor) wrote :
Revision history for this message
maksis (maksis) wrote :

It's not clear that the client should work as you describe. 400kb/s per slot is still slow and the source could possibly replaced with faster ones. Isn't that the reason why you use slow speed disconnecting? How is one user with 400kb/s x 5 better than 5 different users at 400kb/s?

Revision history for this message
Sopor (sopor) wrote :

I think i have found what is wrong. AirDC will detect the user as slow and you will see the user in the 'Re-add source', but it will not disconnect the user. In the screen shot you can see the user is in 'Re-add source' and 'Remove source' at the same time and you find the user in the transfer view as well. I have tried to re-add the user from 'Re-add source', but noting happens because the user is not disconnected and already exists in the 'Remove source' menu.
I have inserted the 'Remove source' menu into the picture (the blue square) so you can see the user is in both menus.

Revision history for this message
Sopor (sopor) wrote :

When i try to re-add the user it will be in both menus instead of disappear from the re-add menu. This will only happens for multislots. When it works the user moves from re-add to remove source. If i turn off multislot (1) it works as it should.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.