Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!udel!princeton!cs!samadams.princeton.edu
From: tr@samadams.princeton.edu (Tom Reingold)
Newsgroups: comp.protocols.tcp-ip
Subject: Are sockets the wave of the future?
Message-ID: <2117@rossignol.Princeton.EDU>
Date: 24 Aug 90 01:54:52 GMT
Sender: news@cs.Princeton.EDU
Organization: Noo Joizy -- The Cultural Mecca
Lines: 24

At my job, we are about to write some applications for running over
TCP/IP on Unix hosts.  We would like to think ahead with portability in
mind.  One day, our code may run on a non-unix host.  And if we write
it in sockets, we may run against a version that is built upon and
supports only STREAMS.  Or will we?

1. What implementations are built on STREAMS?

2. Are they new or old?

3. Are all TCP/IP suites done with sockets nowadays?

4. Is there a reason to consider implementing our code in STREAMS?

5. Currently, our hosts run System V release 3.[23] and have both
libraries.  Which is "the way" to go?

--
	Tom Reingold
	tr@samadams.princeton.edu
	rutgers!princeton!samadams!tr
	201-577-5814
	"Brew strength depends upon the
	 amount of coffee used." -Black&Decker