Assembly: edtFTPnetPRO (in edtFTPnetPRO.dll) Version: 9.4.0.40
Syntax
C# |
---|
public class ConcurrentTransferSettings |
Visual Basic |
---|
Public Class ConcurrentTransferSettings |
Visual C++ |
---|
public ref class ConcurrentTransferSettings |
Remarks
When concurrent transfers are EnabledExFTPConnection (and SecureFTPConnection) will maintain a pool of up to MaxConnections-1 'slave' connections in addition to its own 'main' connection. Many servers limit the number of connections a single client may make to the server, so the number of active connections may be less than MaxConnections.
Interactive applications, such as traditional FTP client apps, can benefit from reserving one connection for user-actions, such as fetching directory listings. Thus when PoolMode is set to [!:PoolMode.ReserveMainConnection] the main connection will not usually be used for transfers. This is not an issue in non-interactive applications in which case the PoolMode may be set to [!:PoolMode.UseMainConnection]. The default value of PoolMode is [!:PoolMode.Automatic] where the main connection will used if ActiveForm is not null.
Although it's generally desirable to reserve the main connection for user interactivity in FTP client-type applications, this cannot be done if the server only permits one connection to the server. If FallBackToMainConnection is set to true (the default) then the main connection will be used for transfers if it is the only possible connection to the server.
If AutoRequeue is enabled then a task that has been given a failed connection will automatically be requeued if at least one connection is still operational.