![]() | |
![]() | Help understanding the globus_xio api |
![]() | Globus XIO introduces a notion of a driver stack to its API |
![]() | The set of interface functions that the driver author must implement to create a driver and the functions to assist in the creation |
![]() | The set of interface functions that the driver author must implement to create a driver and the functions to assist in the creation |
![]() | The File I/O driver |
![]() ![]() | An XIO handle with the file driver can be created with globus_xio_handle_create() |
![]() ![]() | Both the globus_xio_register_read() and globus_xio_register_write() calls follow similar semantics as described below |
![]() ![]() | The file driver uses the following environment variables |
![]() ![]() | File driver specific attrs and cntls |
![]() ![]() | |
![]() ![]() | The File driver is very close to the system code, so most errors reported by it are converted from the system errno |
![]() | This driver implements the HTTP/1.0 and HTTP/1.1 protocols within the Globus XIO framework |
![]() ![]() | An XIO handle with the http driver can be created with either globus_xio_handle_create() or globus_xio_server_register_accept() |
![]() ![]() | The 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 |
![]() ![]() | The globus_xio_server_create() causes a new transport-specific listener socket to be created to handle new HTTP connections |
![]() ![]() | HTTP driver specific attrs and cntls |
![]() ![]() | In addition to errors generated by underlying protocol drivers, the XIO HTTP driver defines a few error conditions specific to the HTTP protocol |
![]() | |
![]() ![]() | An XIO handle with the mode_e driver can be created with either globus_xio_handle_create() or globus_xio_server_register_accept() |
![]() ![]() | Mode E is unidirectional |
![]() ![]() | globus_xio_server_create() causes a mode_e listener to be created and listened upon |
![]() ![]() | The mode_e driver uses the following environment variable |
![]() ![]() | Mode_e driver specific attrs and cntls |
![]() ![]() | |
![]() ![]() | The 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 |
![]() | |
![]() ![]() | Ordering driver is a transform driver and thus has to be used on top of a transport driver |
![]() ![]() | Ordering driver does not allow multiple globus_xio_register_read() to be outstanding |
![]() ![]() | The ordering driver uses the following environment variable |
![]() ![]() | Ordering driver specific attrs and cntls |
![]() ![]() | |
![]() ![]() | The errors reported by ORDERING driver include GLOBUS_XIO_ERROR_COMMAND, GLOBUS_XIO_ERROR_MEMORY, GLOBUS_XIO_ERROR_STATE, GLOBUS_XIO_ERROR_CANCELED |
![]() | The IPV4/6 TCP socket driver |
![]() ![]() | An XIO handle with the tcp driver can be created with either globus_xio_handle_create() or globus_xio_server_register_accept() |
![]() ![]() | Both the globus_xio_register_read() and globus_xio_register_write() calls follow similar semantics as described below |
![]() ![]() | globus_xio_server_create() causes a tcp listener socket to be created and listened upon |
![]() ![]() | The tcp driver uses the following environment variables |
![]() ![]() | Tcp driver specific attrs and cntls |
![]() ![]() | |
![]() ![]() | The TCP driver is very close to the system code, so most errors reported by it are converted from the system errno |
![]() | The IPV4/6 UDP socket driver |
![]() ![]() | An XIO handle with the udp driver can be created with globus_xio_handle_create() |
![]() ![]() | globus_xio_register_read() semantics: |
![]() ![]() | The udp driver uses the following environment variables |
![]() ![]() | UDP driver specific attrs and cntls |
![]() ![]() | |
![]() ![]() | The 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