.TH "globus_xio_tcp_driver_instance" 3 "Version 6.6" "globus_xio" \" -*- nroff -*-
.ad l
.nh
.SH NAME
globus_xio_tcp_driver_instance \- Opening/Closing
.PP
 \- Opening/Closing\&.  

.SH SYNOPSIS
.br
.PP
.SH "Detailed Description"
.PP 
Opening/Closing\&. 

An XIO handle with the tcp driver can be created with either \fBglobus_xio_handle_create()\fP or \fBglobus_xio_server_register_accept()\fP\&.
.PP
If the handle is created with \fBglobus_xio_server_register_accept()\fP, the \fBglobus_xio_register_open()\fP call does nothing more than initialize the internal handle with the accepted socket\&.
.PP
If the handle is created with \fBglobus_xio_handle_create()\fP, and there is no handle set on the attr passed to the \fBglobus_xio_register_open()\fP call, it performs the equivalent of an asynchronous connect() call\&. In this case, the contact string must contain a host name and service/port\&. Both the hostname and port number can be numeric or symbolic (eg: some\&.webserver\&.com:80 or 214\&.123\&.12\&.1:http)\&. If the hostname is symbolic and it resolves to multiple ip addresses, each one will be attempted in succession, until the connect is successful or there are no more addresses\&.
.PP
When the XIO handle is closed, the tcp driver will destroy its internal resources and close the socket (unless this socket was set on an attr)\&. Any write data pending in system buffers will be sent unless the linger option has been set\&. Any remaining data in recv buffers will be discarded and (on some systems) a connection reset sent to the peer\&. 
.SH "Author"
.PP 
Generated automatically by Doxygen for globus_xio from the source code\&.