Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!anasaz!qip!chad
From: chad@qip.UUCP (Chad R. Larson)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Sockets, TLI, or what
Keywords: Socket BSD TLI SystemV
Message-ID: <5632@qip.UUCP>
Date: 5 Dec 90 18:19:02 GMT
References: <9389@ncar.ucar.edu> <2766@cirrusl.UUCP>
Distribution: na
Organization: Anasazi, Inc.  Phoenix, Az
Lines: 33

In article <2766@cirrusl.UUCP> dhesi%cirrusl@oliveb.ATC.olivetti.com
(Rahul Dhesi) writes:
+---------------
| Considering that 99% of existing implementations of UNIX provide no
|                 ^^^^^
| support for TLI, using it at this point would result is extermely
| nonportable code.
+---------------
73.4% of the people who quote statistics make them up.

At our site, we have four different vendors for Unix and three of them
support TLI.  That makes it 25% if you are counting types.  If you count
population of machines, its more like 30 to 5 (or 16%) and the 5 are
scheduled for upgrade.

If you are concerned with portability (and the original poster was), you
can't ignore TLI and streams.  It is the socket interface that will be
going away (but not for a *long* time...).
	-crl
-- 
Chad R. Larson          ...{mcdphx,asuvax}!anasaz!chad or chad@anasaz.UUCP
Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020
(602) 870-3330            "I read the news today, oh boy!"  -- John Lennon


Brought to you by Super Global Mega Corp .com