Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!olivea!tymix!cirrusl!sun600!dhesi
From: dhesi%cirrusl@oliveb.ATC.olivetti.com (Rahul Dhesi)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Sockets, TLI, or what
Keywords: Socket BSD TLI SystemV
Message-ID: <2766@cirrusl.UUCP>
Date: 4 Dec 90 20:34:22 GMT
References: <9389@ncar.ucar.edu>
Sender: news@cirrusl.UUCP
Distribution: na
Organization: Cirrus Logic Inc.
Lines: 20

In <9389@ncar.ucar.edu> davis@groucho.ucar.edu (Glenn P. Davis) writes:

>(He has been reading the Sun "Network Programming Guide" which
>contains a warning that "Socket based IPC is no longer the preferred
>framework for transport level programming....").

This comes from the AT&T SVR4 manuals and represents a corporate "party
line" rather than any practising software engineer's opinion.
Considering that 99% of existing implementations of UNIX provide no
support for TLI, using it at this point would result is extermely
nonportable code.

SVR4 is still in its infancy.  Except for a few bugs, it supports the
socket interface.  Since no existing software uses AT&T's TLI, which is
very new and untested, your best bet is to (a) use the socket interface
but (b) make sure your code doesn't trigger the socket-related bugs in
SVR4, which are documented in the AT&T manuals.
--
Rahul Dhesi <dhesi%cirrusl@oliveb.ATC.olivetti.com>
UUCP:  oliveb!cirrusl!dhesi


Brought to you by Super Global Mega Corp .com