Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!news.mathworks.com!fu-berlin.de!irz401!orion.sax.de!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Sys V Streams Vs. BSD Sockets Date: 25 Mar 1997 00:24:09 GMT Organization: Private BSD site, Dresden Lines: 22 Message-ID: <5h75v9$ta@uriah.heep.sax.de> References: <5h4rte$92a@news.interlog.com> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.6 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37686 paulg@gold.interlog.com (Paul Griffith) wrote: > I know this is a generic Unix question (if there is such a thing), but > where can I find a FAQ on the major differences in streams and sockets > ? Is one better for some tasks ?? I don't know where you can find a good overview. Anyway, one of the worst mistakes of SysV has it been to implement the IP layers on top of STREAMS. It's nothing but slow. STREAMS are good for implementing things like terminal line disciplines, maybe even for slow networking services (like ISDN). STREAMS are not a networking API (sockets are), but a kernel implementation detail. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)