udp_driver_errors(3) [debian man page]

Error Types(3)							    globus xio							    Error Types(3)

NAME

       Error Types -

   Enumerations
       enum globus_xio_udp_error_type_t { GLOBUS_XIO_UDP_ERROR_NO_ADDRS, GLOBUS_XIO_UDP_ERROR_SHORT_WRITE }

Detailed Description
       The UDP driver is very close to the system code, so most errors reported by it are converted from the system errno.

       A few of the exceptions are GLOBUS_XIO_ERROR_COMMAND, GLOBUS_XIO_ERROR_CONTACT_STRING, GLOBUS_XIO_ERROR_CANCELED,
       GLOBUS_XIO_UDP_ERROR_NO_ADDRS, and GLOBUS_XIO_UDP_ERROR_SHORT_WRITE

       See also:
	   globus_xio_driver_error_match()

	   globus_error_errno_match()

Enumeration Type Documentation
   enum globus_xio_udp_error_type_t
       UDP driver specific error types.

       Enumerator:

       GLOBUS_XIO_UDP_ERROR_NO_ADDRS
	      Indicates that no IPv4/6 compatible sockets could be resolved for the specified hostname.

       GLOBUS_XIO_UDP_ERROR_SHORT_WRITE
	      Indicates that a write of the full buffer failed. Possibly need to increase the send buffer size.

Author
       Generated automatically by Doxygen for globus xio from the source code.

Version 3.3							  Mon Apr 30 2012						    Error Types(3)

Reading/Writing(3)						    globus xio							Reading/Writing(3)

NAME

       Reading/Writing - globus_xio_register_read() semantics:

       If the waitforbytes parameter is greater than zero, the read will happen asynchronously and be completed when at least waitforbytes has
       been read/written.

       If the waitforbytes parameter is equal to zero, one of the following alternative behaviors occur:

       If the length of the buffer is > 0 the read happens synchronously. If the user is using one of the blocking xio calls, no internal callback
       will occur.

       If the length of the buffer is also 0, the call behaves like an asynchronous notification of data ready to be read. ie, an asynchronous
       select().

       In any case, when an error occurs before the waitforbytes request has been met, the outgoing nbytes is set to the amount of data actually
       read before the error occurred.

       If the handle is not connected, the user should pass in a data descriptor. After the read, this data_descriptor will contain the contact
       string of the sender. The user can either get this contact string with GLOBUS_XIO_UDP_GET_CONTACT or pass the data descriptor directly to
       globus_xio_register_write() to send a message back to the sender.

       Also, if the handle is not connected, the waitforbytes should probably be 1 to guarantee that only one packet is received and the sender
       contact isnt overwritten by multiple packets from different senders.

       globus_xio_register_write() semantics:

       When performing a write, exactly one UDP packet is sent of the entire buffer length. The waitforbytes parameter is ignored. If the entire
       buffer can not be written, a GLOBUS_XIO_UDP_ERROR_SHORT_WRITE error will be returned with nbytes set to the number of bytes actually sent.

       If the handle is not 'connected', a contact string must be set in the data descriptor to globus_xio_register_write(). This can either be
       done explicitly with GLOBUS_XIO_UDP_SET_CONTACT or implicitly by passing in a data descriptor received from globus_xio_register_read().

       The udp write semantics are always synchronous. No blocking or internal callback will occur when using globus_xio_write().

Author
       Generated automatically by Doxygen for globus xio from the source code.

Version 3.3							  Mon Apr 30 2012						Reading/Writing(3)