Jump to content

Talk:X/Open Transport Interface

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Review

[edit]

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

  • Thank you!

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.

  • You mean Network Services Library, but although this library is usually found on UNIX systems it's not part of XTI specification. This article refers only to X/Open Transport Interface. Without this library, applications have to know how to select a particular transport. This is why, XTI by it self, is not a protocol independent way of developing applications. I saw you removed my reference to IBM published red book work(Introduction to Networking Technologies) that explains why XTI doesn't provide a transparent access to underlaying transports. Please undo.
See XNS.5 Appendix E. The NSL (present in SVID) is such a network directory/network selection mechanism as is described. Also see XNS.5 Appendix C.4. — Dgtsyb (talk) 15:43, 28 July 2009 (UTC)[reply]

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.

  • Beside of what I said about libnsl at previous point you mean using XTI to communicate over a TCP provider. XTI was designed to work on a variety of transports like SPX or NetBIOS that doesn't have this limitation. Not even all Berkeley Sockets implementations have this limitation(see winsock)! Please undo.
See XNS.5 t_bind(). [TACCES] the user does not have permission to use the specified address. This is what happens if the user tries to bind to a privileged port. XNS.5 Appendix E and the NSL library as an implementation of the network directory/network selection capability described there provide for address splitting and broadcast address in a transport protocol independent fashion. — Dgtsyb (talk) 15:43, 28 July 2009 (UTC)[reply]

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.

  • get/setsockopt has 'level' parameter that tells to get/set option to network/transport level. XTI referring only to transport it can only affect transport level options, so please undo.
See XNS.5 t_optmgmt() and the XTI-LEVEL options described there that are equivalent (almost identical) to SO_SOCKET level options. — Dgtsyb (talk) 15:43, 28 July 2009 (UTC)[reply]

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

  • XTI is replacing TLI so probably Transport Layer Interface needs to be merged here. Anyway, they can both co-exist separately as ATM and MPLS exists now.

Please undo all those points as they were good! Alecssicius (talk) 17:44, 27 July 2009 (UTC)[reply]

Merge into Transport Layer Interface

[edit]

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]

[edit]

Hello fellow Wikipedians,

I have just modified one external link on X/Open Transport Interface. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 13:32, 21 July 2016 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:X/Open_Transport_Interface&oldid=1201470348"