|
Module descriptor. The Globus FTP Control library uses the standard module activation and deactivation API to initialize it's state. Before any GSIFTP functions are called, the module must be activated
globus_module_activate(GLOBUS_GSIFTP_CONTROL_MODULE); This function returns GLOBUS_SUCCESS if the GSIFTP library was successfully initialized. This may be called multiple times. To deactivate the GSIFTP library, the following must be called
globus_module_deactivate(GLOBUS_GSIFTP_CONTROL_MODULE); |
|
control structure types. The enumeration values match the character value of the argument to TYPE. |
|
control structure mode
|
|
control dcau types
|
|
control dcau subject authentication type
|
|
control striping Types
|
|
control striping round robin attribute structure
|
|
control dcau union
|
|
control striping attribute union
|
|
control structure structure
|
|
control parallelism Types
|
|
control parallelism attribute structure
|
|
TCP Buffer Setting Modes.
|
|
Automatically set the TCP buffer/window size.
|
|
control tcpbuffer attribute structure
|
|
Authentication Values. This structure is populated and passed back to the user via the globus_ftp_control_auth_callback_t(). It contains the information needed to decide if a client may use the server. |
|
Asynchronous operation completion callback. This callback is called whenever a reply to command is received on the FTP control channel. It allows the user to handle the received reply or alternatively handle any errors that occurred during the interaction with the FTP server. This function will be called multiple times in the case when intermediate responses (1yz) are received.
|
|
Asynchronous control callback. This callback is used as a generic control operation callback.
|
|
Server command callback. When a command from a client is received on the control channel a user callback with this signature is called.
|
|
Server authentication complete callback. A function with this signature is registered by calling globus_ftp_control_accept(). It is called when the authentication protocal has completed. Based on the auth_result, the server implementor should determine authorization and then send the appropriate response using globus_ftp_control_send_response(), indicating to the client whether authorization was successful or not.
|
|
Authentication requirements. The value of this should be a bitwise or of
|
|
Asynchronous data transmission operation callback. This callback is called in functions that send or receive data on the data channel(s). In the case of a write, this function is invoked when the entire data buffer is sent. Depending on the data transfer properties set by the globus_ftp_control_local_*() functions, the data may actually be split into multiple buffers and sent to multiple data nodes. In the case of a read, this function will return a single extent of the data. The order of the data returned is not defined in an extended block mode data transfer. It is up to the user of the API to re-construct the file order.
|
|
Server callback. A functions with this signature can be used as general callbacks for the GSIFTP server API.
|
|
control structure types. The enumeration values match the character value of the argument to TYPE. |
|
control structure mode
|
|
control dcau types
|
|
control striping Types
|
|
control protection levels
|
|
delayed passive flags
|
|
control structure structure
|
|
control parallelism Types
|
|
TCP Buffer Setting Modes.
|
|
Update the handle with the layout and the size of the data sent over the data channel. This function is deprecated. The interface will be the changed to that of globus_X_ftp_control_local_layout()
|
|
Create an outgoing FTP data connection. This function sets the interface that will be used to send and receive information along the data channel.
|
|
Create a globus_ftp_control_data_write_info_t structure. This funciton populates a globus_ftp_control_data_callback_t structure with valid information. This structure provides the user a way to register several data writes with a single callback. This is quite useful to the writter of enqueue functions. It allows a single call to globus_ftp_control_data_write() to be broken up into many writes, potentially on different stripes, and for a single callback to be called when all are finished.
|
|
Release a data_info structure. This function releases all memory and references created when a call to globus_ftp_control_create_data_info() was made. For every call to globus_ftp_control_create_data_info() a call to this function must be made.
|
|
Write FTP data to a particular stripe. This function allows the user to write to a specified stripe. The stripe index relates to the order passsed into local_spor(). This function differs from globus_ftp_control_data_write() in that no enqueue function is needed since the user specifies the stripe on which data is written. In order to use this function the user must have a valid pointer to a globus_ftp_control_data_write_info_t structure. The data_info structure can be obtained by a call to globus_ftp_control_create_data_info(). Many calls to this function can be made, but only a single user callback occurs per creation of a globus_ftp_control_data_write_info_t structure.
|
|
Write data on a specific stripe from an enqueue callback function only. This function allows the user to register the write of ftp data on a specfic stripe. This function can only be called fromed an enqueue function callback. This function should be used only by the implementor of an enqueue funciton. It should be viewed as unstable and used used only by advanced users. This is the only function in the library that the enqueue function implemtor is allowed from the enqueue callback.
|
about globus |
globus toolkit |
dev.globus
Comments? webmaster@globus.org