Modules
Here is a list of all modules:
[detail level 12]
oThe globus_xio user API.
oUser API Assistance.
Help understanding the globus_xio api
oGlobus XIO DriverGlobus XIO introduces a notion of a driver stack to its API
oDriver ProgrammingThe set of interface functions that the driver author must implement to create a driver and the functions to assist in the creation
oDriver Programming: String optionsThe set of interface functions that the driver author must implement to create a driver and the functions to assist in the creation
oGlobus XIO File DriverThe File I/O driver
|oOpening/ClosingAn XIO handle with the file driver can be created with globus_xio_handle_create()
|oReading/WritingBoth the globus_xio_register_read() and globus_xio_register_write() calls follow similar semantics as described below
|oEnv VariablesThe file driver uses the following environment variables
|oAttributes and CntlsFile driver specific attrs and cntls
|oTypes
|\Error TypesThe File driver is very close to the system code, so most errors reported by it are converted from the system errno
oGlobus XIO HTTP DriverThis driver implements the HTTP/1.0 and HTTP/1.1 protocols within the Globus XIO framework
|oOpening/ClosingAn XIO handle with the http driver can be created with either globus_xio_handle_create() or globus_xio_server_register_accept()
|oReading/WritingThe HTTP driver behaves similar to the underlying transport driver with respect to reads and writes with the exception that metadata must be passed to the handle via open attributes on the client side and will be received as data descriptors as part of the first request read or response read
|oServerThe globus_xio_server_create() causes a new transport-specific listener socket to be created to handle new HTTP connections
|oAttributes and CntlsHTTP driver specific attrs and cntls
|\Error TypesIn addition to errors generated by underlying protocol drivers, the XIO HTTP driver defines a few error conditions specific to the HTTP protocol
oGlobus XIO MODE_E Driver
|oOpening/ClosingAn XIO handle with the mode_e driver can be created with either globus_xio_handle_create() or globus_xio_server_register_accept()
|oReading/WritingMode E is unidirectional
|oServerglobus_xio_server_create() causes a mode_e listener to be created and listened upon
|oEnv VariablesThe mode_e driver uses the following environment variable
|oAttributes and CntlsMode_e driver specific attrs and cntls
|oTypes
|\Error TypesThe errors reported by MODE_E driver include GLOBUS_XIO_ERROR_COMMAND, GLOBUS_XIO_ERROR_MEMORY, GLOBUS_XIO_ERROR_STATE, GLOBUS_XIO_ERROR_PARAMETER, GLOBUS_XIO_ERROR_EOF, GLOBUS_XIO_ERROR_CANCELED, GLOBUS_XIO_MODE_E_HEADER_ERROR
oGlobus XIO ORDERING Driver
|oOpening/ClosingOrdering driver is a transform driver and thus has to be used on top of a transport driver
|oReading/WritingOrdering driver does not allow multiple globus_xio_register_read() to be outstanding
|oEnv VariablesThe ordering driver uses the following environment variable
|oAttributes and CntlsOrdering driver specific attrs and cntls
|oTypes
|\Error TypesThe errors reported by ORDERING driver include GLOBUS_XIO_ERROR_COMMAND, GLOBUS_XIO_ERROR_MEMORY, GLOBUS_XIO_ERROR_STATE, GLOBUS_XIO_ERROR_CANCELED
oGlobus XIO TCP DriverThe IPV4/6 TCP socket driver
|oOpening/ClosingAn XIO handle with the tcp driver can be created with either globus_xio_handle_create() or globus_xio_server_register_accept()
|oReading/WritingBoth the globus_xio_register_read() and globus_xio_register_write() calls follow similar semantics as described below
|oServerglobus_xio_server_create() causes a tcp listener socket to be created and listened upon
|oEnv VariablesThe tcp driver uses the following environment variables
|oAttributes and CntlsTcp driver specific attrs and cntls
|oTypes
|\Error TypesThe TCP driver is very close to the system code, so most errors reported by it are converted from the system errno
\Globus XIO UDP DriverThe IPV4/6 UDP socket driver
 oOpening/ClosingAn XIO handle with the udp driver can be created with globus_xio_handle_create()
 oReading/Writingglobus_xio_register_read() semantics:
 oEnv VariablesThe udp driver uses the following environment variables
 oAttributes and CntlsUDP driver specific attrs and cntls
 oTypes
 \Error TypesThe UDP driver is very close to the system code, so most errors reported by it are converted from the system errno

about globus | globus toolkit | dev.globus

Comments? webmaster@globus.org