Talk:X/Open Transport Interface

Review

In reviewing this new page, I added a number of primary and secondary sources.

The section on protocol independence is incorrect. It is probably better to say that XTI/TLI, being protocol agnostic, permits the application be protocol or transport independent, but does not help it do so. The Sun TI-RPC Network Selection Library (NSL) components, normally used with all XTI applications, provides such assistance.

The contrast to sockets is also incorrect. XTI supports the concept of privileged ports (T_ACCESS error on bind). The Network Selection Library (NSL) provides the means for protocol independent splitting of a host and service component of an address. Broadcast addresses as also supported. The NSL library components supporting these are equivalent to the equivalent Sun RPC BSD sockets functions.

Specific mappings of XTI interface to Sockets interface is not quite correct. Equivalence is better than listed and is provided by the underlying TPI upon which both are implemented in SVR 4.2 based systems.

The statement that XTI does not support options at other than the transport layer is simply incorrect. The only options that differ are the XTI-level options which differ slightly from Socket-level options. Options at other levels are almost identical.

This page should probably be merged with Transport Layer Interface. — Dgtsyb (talk) 02:57, 24 July 2009 (UTC)[reply]

Merge into Transport Layer Interface

I agree with User:Dgtsyb and strongly suggest to merge this into the TLI article, so the evolution from original TLI to the X/Open spec doesn't require duplication in both articles. Kbrose (talk) 21:14, 25 July 2009 (UTC)[reply]