Guidelines to Protocol Independence

XTI/TLI's set of services, common to many transport protocols, offers protocol independence to applications. Not all transport protocols support all XTI/TLI services. If software must run in a variety of protocol environments, use only the common services. The following is a list of services that might not be common to all transport protocols.

1. In connection mode service, a transport service data unit (TSDU) might not be supported by all transport providers. Make no assumptions about preserving logical data boundaries across a connection.

2. Protocol and implementation specific service limits are returned by the t_open(3NSL) and t_getinfo(3NSL) routines. Use these limits to allocate buffers to store protocol-specific transport addresses and options.

3. Do not send user data with connect requests or disconnect requests, such as t_connect(3NSL) and t_snddis(3NSL). Not all transport protocols work this way.

4. The buffers in the t_call structure used for t_listen(3NSL) must be large enough to hold any data sent by the client during connection establishment. Use the T_ALL argument to t_alloc(3NSL) to set maximum buffer sizes to store the address, options, and user data for the current transport provider.

5. Do not specify a protocol address on t_bind(3NSL) on a client side endpoint. Let the transport provider assign an appropriate address to the transport endpoint. A server should retrieve its address for t_bind(3NSL) in such a way that it does not require knowledge of the transport provider's name space.

6. Do not make assumptions about formats of transport addresses. Transport addresses should not be constants in a program. Chapter 4, Transport Selection and Name-to-Address Mapping contains detailed information.

7. The reason codes associated with t_rcvdis(3NSL) are protocol-dependent. Do not interpret this information if protocol independence is important.

8. The t_rcvuderr(3NSL) error codes are protocol dependent. Do not interpret this information if protocol independence is a concern.

9. Do not code the names of devices into programs. The device node identifies a particular transport provider and is not protocol independent. See Chapter 4, Transport Selection and Name-to-Address Mapping for details.

10. Do not use the optional orderly release facility of the connection mode service--provided by t_sndrel(3NSL) and t_rcvrel(3NSL)--in programs targeted for multiple protocol environments. This facility is not supported by all connection-based transport protocols. Its use can prevent programs from successfully communicating with open systems.