Bug #49488
Controlling: reconnect states?
Status: | Assigned | Start date: | 08/20/2014 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | % Done: | 0% | ||
Category: | Controlling | |||
Target version: | 020 - Next Release 2.0 | |||
Resolution: |
Description
An example:
1 HosterA PrioHigh
2 HosterA PrioHigh
3 HosterB PrioLow
4 HosterB PrioLow
Sequential download is configured (only 1 connection).
A) When CFG "..PrefersReconnect" is false, it is:
[1] [3] reconnect [2] [4]
B) When CFG "..PrefersReconnect" is true, it should be:
[1] reconnect [2] [3] reconnect [4]
but it's like in A)
Another problem with A) is, that it ignores Priorities.
Even when CFG "..PrefersReconnect" set to false, JD2 should
reconnect after [1] and not continue with a lower Prio.
Another problem is, that JD2 reconnects even after a Stopmark
stopped all downloads.