These features are operation independent.
The attribute which can currently set on a handle concern the connection caching behavior of the handle, and the associations of plugins with a handle.
|
Handle Attributes. Handle attributes are used to control the caching behavior of the ftp client handle, and to implement the plugin features for reliability and performance tuning.
|
|
Initialize an FTP client handle attribute set. This function creates an empty FTP Client handle attribute set. This function must be called on each attribute set before any of the other functions in this section may be called.
|
|
Destroy an FTP client handle attribute set. This function destroys an ftp client handle attribute set. All attributes on this set will be lost. The user must call globus_ftp_client_handleattr_init() again on this attribute set before calling any other handle attribute functions on it.
|
|
Create a duplicate of a handle attribute set. The duplicated attribute set has a deep copy of all data in the attribute set, so the original may be destroyed while the copy is still valid.
|
|
Set/Get the cache all connections attribute for an ftp client handle attribute set. This attribute allows the user to cause all control connections to be cached between ftp operations. When this is enabled, the user skips the authentication handshake and connection establishment overhead for multiple subsequent ftp operations to the same server. Memory and network connections associated with the caching will be used until the handle is destroyed. If fine grained caching is needed, then the user should disable this attribute and explicitly cache specific URLs.
|
|
Enable/Disable rfc1738 support for non-root relative URLs.
|
|
Enable/Disable GridFTP2 [GFD.41] support for servers supporting it.
|
|
Enable/Disable command queueing for pipelined transfers.
|
|
Enable/Disable caching for a specific URL. This function adds/removes the specified URL into the default cache for a handle attribute. Handles initialized with this attr will keep connections to FTP servers associated with the URLs in its cache open between operations.
|
|
Enable/Disable caching for a specific URL. This function adds/removes the specified URL into the default cache for a handle attribute. Handles initialized with this attr will keep connections to FTP servers associated with the URLs in its cache open between operations.
|
|
Set the netlogger handle used with this transfer. Each handle can have a netlogger handle associated with it for logging its data. Only 1 netlogger handle can be associated with a client handle.
|
|
Add/Remove a plugin to a handle attribute set. Each handle attribute set contains a list of plugins associated with it. When a handle is created with a particular attribute set, it will be associated with a copy of those plugins. Only one instance of a specific plugin may be added to an attribute set. Each plugin must have a different name. A copy of the plugin is created via the plugins 'copy' method when it is added to an attribute set. Thus, any changes to a particular plugin must be done before the plugin is added to an attribute set, and before the attribute set is used to create handles.
|
|
Set/Get the cache all connections attribute for an ftp client handle attribute set. This attribute allows the user to cause all control connections to be cached between ftp operations. When this is enabled, the user skips the authentication handshake and connection establishment overhead for multiple subsequent ftp operations to the same server. Memory and network connections associated with the caching will be used until the handle is destroyed. If fine grained caching is needed, then the user should disable this attribute and explicitly cache specific URLs.
|
|
Enable/Disable rfc1738 support for non-root relative URLs.
|
|
Enable/Disable GridFTP2 [GFD.41] support for servers supporting it.
|
|
Enable/Disable command queueing for pipelined transfers.
|
|
Set the netlogger handle used with this transfer. Each handle can have a netlogger handle associated with it for logging its data. Only 1 netlogger handle can be associated with a client handle.
|
|
Add/Remove a plugin to a handle attribute set. Each handle attribute set contains a list of plugins associated with it. When a handle is created with a particular attribute set, it will be associated with a copy of those plugins. Only one instance of a specific plugin may be added to an attribute set. Each plugin must have a different name. A copy of the plugin is created via the plugins 'copy' method when it is added to an attribute set. Thus, any changes to a particular plugin must be done before the plugin is added to an attribute set, and before the attribute set is used to create handles.
|
about globus |
globus toolkit |
dev.globus
Comments? webmaster@globus.org