|
Create an incoming FTP data connection. This function will register a globus_io_{accept, connect}. Further accepts/connects are done by registering a new accept/connect in the current accept/connect callback. A call to either globus_ftp_control_local_pasv() or globus_ftp_control_local_port() needs to precede this calling this function. This function may be followed by a globus_ftp_data_read.
|
|
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 an outgoing FTP data connection. This function will register a globus_io_{accept, connect}. Further accepts/connects are done by registering a new accept/connect in the current accept/connect callback. A call to either globus_ftp_control_local_pasv() or globus_ftp_control_local_port() needs to precede this calling this function. This function may be followed by a globus_ftp_data_write.
|
|
Opens additional data channels (connections) to the host identified by the stripe parameter.
|
|
Sends an eof message to each stripe along an open data connection.
|
|
Removes data channels (connections) to the host identified by the stripe parameter.
|
|
Returns the number of currently open channels for the host identified by the stripe parameter. This number may be less then the level of parallelism specified in local_parallelism, due to the possibility that some channels have not yet connected.
|
|
Returns the total number of data channels used so far in the current transfer on the given stripe.
|
|
Determines if the library will automatically send an EOF message in extended block mode, or if the user will have to explicitly do it by calling globus_ftp_control_data_send_eof().
|
|
Set the parallelism information in a FTP control handle.
|
|
Create a local listening socket, bind it and return the address the socket is listening to. If there is a existing data connection it is closed.
|
|
Create num_addresses local listening sockets, bind them and return the addresses the sockets are listening to. If there is a existing data connection it is closed.
|
|
Insert the host/port information returned by a PASV on the remote host into the local FTP control handle. (close any outstanding data con)
|
|
Insert the host/port addresses returned by a SPAS on the remote host into the local FTP control handle. If there are any outstanding data connections at this point, they are closed.
|
|
Update the FTP control handle with the given type information.
|
|
Update the FTP control handle with the given mode information.
|
|
Update the FTP control handle with the given socket buffer information.
|
|
Update the FTP control handle with the given data channel authentication information. If authentication is set to GLOBUS_FTP_CONTROL_DCAU_NONE, then protection will also be disabled for this control handle.
|
|
Update the FTP control handle with the given protection buffer size information. This function sets protection buffer size to be used by this handle. This value is used to determine how much data will be sent in each packet during a protected data transfer.
|
|
Query the FTP control handle for the protection buffer size information. This function queries the handle to determine the protection buffer size which is used by this handle. This value is used to determine how much data will be sent in each packet during a protected data transfer.
|
|
Updates the handle with information on the structure of the data being sent on the data channel. This function updates the handle with the provided structure information. At this point the only structure type that is supported is the file type.
|
|
Writes data from the supplied buffer to data connection(s). This function writes contained in the buffer to the data channel(s).
|
|
Reads data from data connection(s) and put them in the supplied buffer. This function takes the given buffer and will try to read data from the data connection(s).
|
|
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 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.
|
|
Forces an imediate close of all data connections.
|
about globus |
globus toolkit |
dev.globus
Comments? webmaster@globus.org