Specifically, they are used to register multiple byte range buffers with a file transfer request, and to query the state of a transfer in-progress.
To implement a server, the request handle is populated by the protocol module implementation. The server may use the functions in this section to determine information about what the client is requesting.
To implement a client, the request handle should be queried after the blocking call or initial callback has been invoked to determine if the request has been authorized or referred, and after EOF, to determine whether the request has completed successfully.
A request handle contains a pointer which may be used by the handler of the request to store a pointer to arbitrary application-specific data.
|
Type of operation associated with a request handle.
|
|
|
Determine the type of a request. This function is used by GASS server implementations to discover what type of operation the client is requesting for an URL.
|
|
Get the user pointer associated with a request. This function extracts the user pointer from a request handle. The user-pointer may be used by the application which is generating or servicing the request to store a pointer to any application-specific piece of data.
|
|
Set the user pointer associated with a request handle. This function sets the user pointer from a request handle. The user-pointer may be used by the application which is generating or servicing the request to store a pointer to any application-specific piece of data.
|
|
Check the status of a request. This function queries a request to determine the status of the request. This function should be called after EOF has been reached, or after the initial get, put, or append has returned or had it's callback function called to determine if it is possible to procede, or whether the file transfer was successfully processed.
|
|
Extract referral information from a request handle. This function queries the request handle to determine any referral information that it contains. This function should only be called on request handles in the GLOBUS_GASS_TRANSFER_REQUEST_REFERRED state. If no referral information is stored in the request handle, then the referral will be initialized to an empty referral. The referral must be destroyed by calling globus_gass_transfer_referral_destroy() by the caller.
|
|
Get the URL from a request handle. This function queries the request handle to determine the URL associated with the request. This function is intended to be useful to GASS server implementors.
|
|
Get the length of a file to be transferred using GASS. This function queries the request handle to determine the amount of data that will be transferred to copy the URL. The length may be GLOBUS_GASS_TRANSFER_LENGTH_UNKNOWN if the sender can not determine the length before making or authorizing the request.
|
|
Set the type of a request. This function modifies a request handle by setting the type of operation that it is being used for. This function may only be called once per handle, and only from a GASS protocol module implementation.
|
|
Set the URL to which a request handle refers. This function modifies the given request handle so that it's URL field is set to string pointed to by url. No copy is made of the string, so the caller must not free it. It must be allocated by calling one of the memory allocators in globus_libc, as it will be freed when the request handle is destroyed. This function must only be called by protocol modules when constructing a request handle when accepting a new request. This function can only be called once per request handle.
|
|
Set the length of a transfer associated request handle. This function modifies the given request handle so that it's length field is set to give length parameter. This function must only be called by protocol modules when constructing a request handle when receiving the response to a get request. This function can only be called once per request handle.
|
|
Get an integer code describing why the request was denied. This function queries a request which was denied by a server to determine why it was denied. The denial reason will be expressed in a protocol-specific response code. Knowledge of the protocol is needed to understand this response.
|
|
Get an string describing why a request was denied. This function queries a request which was denied by a server to determine why it was denied. The denial reason will be expressed as a response string. The string must be freed by the caller.
|
|
Get the subject string associated with a request. This function queries a request handle to determine the subject identity of the client who initiated the request. The string must not be freed by the caller.
|
|
Destroy a request handle. This function destroys the caller's reference to a request handle. It must be called for all request handles which are created by calling functions in the "Client-Initiated Operations" or "Implementing Servers" sections of this manual. After calling the function, the caller must not attempt to use the request handle for any purpose.
|
about globus |
globus toolkit |
dev.globus
Comments? webmaster@globus.org