Provided by: libglobus-xio-doc_3.6-2_all bug


       Reading/Writing - Ordering driver does not allow multiple globus_xio_register_read() to be

       This limitation is there to enforce that the users get the read callback in order. There
       is a known issue in enforcing the order in which read callbacks are delivered with
       multiple outstanding reads. This limitation does not restrict the use of parallel reads
       feature provided by the underlying transport driver.
       GLOBUS_XIO_ORDERING_SET_MAX_READ_COUNT on the attr can be used to specify the number of
       parallel reads. Ordering will have a maximum of this many number of reads outstanding to
       the driver below it on the stack. It buffers the data read and delivers it to the user in

       globus_xio_register_write() does not enforce any restriction.


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