Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!spool.mu.edu!pravda.aa.msen.com!nntp.coast.net!howland.reston.ans.net!newsfeed.internetmci.com!netnews.nwnet.net!nwnet.net!not-for-mail From: aad@nwnet.net (Anthony D'Atri) Newsgroups: comp.unix.bsd.netbsd.misc,comp.unix.bsd.bsdi.misc,comp.unix.solaris,comp.unix.aix Subject: Re: ISP hardware/software choices (performance comparison) Date: 2 Feb 1996 13:53:06 -0800 Organization: NorthWestNet, Bellevue, WA Lines: 14 Distribution: inet Message-ID: <4eu142$bnt@olympus.nwnet.net> References: <4cmopu$d35@vixen.cso.uiuc.edu> <4digkr$83u@mail.fwi.uva.nl> <4e6o44$4rd@park.uvsc.edu> <4e7mrc$ics@mail.fwi.uva.nl> Reply-To: aad@nwnet.net NNTP-Posting-Host: olympus.nwnet.net Xref: euryale.cc.adfa.oz.au comp.unix.bsd.netbsd.misc:2209 comp.unix.bsd.bsdi.misc:2355 comp.unix.solaris:59506 comp.unix.aix:70447 >sockets have shortcomings, TLI tried to rectify those (but missed >the target). One of the things you cannot do in sockets is write >code that just as easily connects to Unix domain/TCP or OSI >endpoints. You need to know what types of addresses your are manipulating >and code for that particular address familily. Does anyone really care about OSI any more, though? I remember a handful of years ago when claims were made that it was going to supplant the TCP/IP suite, but from what I can tell that never happened.