A stream tube is a transport for ordered, reliable data transfer, similar to SOCK_STREAM sockets.
When offering a stream tube, the initiating client creates a local
listening socket and offers it to the recipient client using the
A string representing the service name that will be used over the tube. It should be a well-known TCP service name as defined by http://www.iana.org/assignments/port-numbers or http://www.dns-sd.org/ServiceTypes.html, for instance "rsync" or "daap".
When the tube is offered, the service name is transmitted to the other end.
When requesting a channel with
A mapping from address types (members of Socket_Address_Type) to arrays of access-control type (members of Socket_Access_Control) that the connection manager supports for stream tubes with that address type. For simplicity, if a CM supports offering a particular type of tube, it is assumed to support accepting it.
A typical value for a host without IPv6 support:
{ Socket_Address_Type_IPv4: [Socket_Access_Control_Localhost, Socket_Access_Control_Port, Socket_Access_Control_Netmask], Socket_Address_Type_Unix: [Socket_Access_Control_Localhost, Socket_Access_Control_Credentials] }
Connection Managers MUST support at least IPv4 with the localhost access control.
When requesting a channel with