Simultanius connections to primary and backup servers

[TheFireman]

As it is now, when you have defined say 3 connections for your primary server, and 1 for a backup server, when an article is not found on the primary sever, one connection of the primary server is killed and is used for the backup server. So instead of having 3+1 connections in total, you only have 3 connections.

This is a problem, when using a speed/connection capped primary provider (e.g. Octanews, 3 connections x 128kbps) and the speed of your connection is bigger than the speed you can get from your primary provider.

The connections needed for the backup servers should not interfear with the connections of the primary server.

[meltcity]

Specifying the number of connections for the backup server also has no effect.

Let's say you set the primary server to 3 connections and the backup server to 1 connection, as in the above example. If none of the articles are found in the 3 open threads in the primary server, alt.binz will automatically try to download them from the backup server using the same 3 threads, even though you have only specified only 1 allowed connection for the backup. This can be a problem if your backup server allows fewer connections than your primary.

To avoid refused connections I have to set the number of primary connections to 3 because that is the maximum allowed by my backup server, even though my primary server allows 8 connections. Luckily this has minimal effect on download speed.

[Gompy]

Specifying the number of connections for the backup server also has no effect.

Let's say you set the primary server to 3 connections and the backup server to 1 connection, as in the above example. If none of the articles are found in the 3 open threads in the primary server, alt.binz will automatically try to download them from the backup server using the same 3 threads, even though you have only specified only 1 allowed connection for the backup. This can be a problem if your backup server allows fewer connections than your primary.

This is the "issue" I'm running against also.
Using 3 servers, 2 from ISP and 1 payserver.
ISP have 2 servers, set server nr-1 from ISP as primary.
Set server nr-2 from ISP as backup.
Set payserver as backup, with just 1 connection to the payserver.

Than the "problem".
I've got a shared account by the payserver, which allow me just 1 connection.
If a part isn't found at the ISP-servers, then at least 2 connections  will be started to the payserver, which gives problems with the other members of the account.

Perhaps there is a other way to setup the servers, but of what I've noticed, every setup I've done leads to more then 1 connection to the payserver.

I'm sure it has nothing to do with a bug, it's more of how the program is working and maybe this should be placed under " requests", but my message joins more or less the previous.

Regards, Gompy