Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!emory!stiatl!bagend!bvsatl!root
From: root@bvsatl.UUCP (Super user)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Are sockets the wave of the future?
Summary: sockets obituary a bit premature
Message-ID: <181@bvsatl.UUCP>
Date: 27 Aug 90 21:51:37 GMT
References: <9008242107.AA19843@ucbvax.Berkeley.EDU> <1990Aug25.183437.1@rogue.llnl.gov>
Organization: bvsatl   Atlanta Ga.
Lines: 39


Any obituaries for the sockets programming interface are a bit premature.

I admit that for many systems, Streams are preferable to sockets. However
most streams based systems also layer a sockets interface on top of
the "native" streams. "Why is this?", you may ask. How many public domain
programs do you see using the sockets interface? How many do you see
using the streams interface? 
People who want to make their jobs easier will try to
build upon the existing code base. Much of that code base written to
run on sockets. 

In addition to the inertia of all that existing code, some
systems only support the sockets interface. For instance, many embedded
systems are fairly lean implementations that do not include a streams
implementation. I would bet that most routers, terminal servers,
etc are built on sockets interfaces. If you had to add a new capability
(like SNMP for instance) to such a device, you would use the existing 
services.

There are a lot of weird devices now supporting TCP/IP. For instance,
I just worked on a implementation team that ported TCP/IP (and sockets)
to HP BASIC workstations, believe that or not.  It was difficult
enough to make a usable BASIC->sockets interface. Streams for basic would
be incredibly weird. In order
to bring a large number of diverse systems into the internet fold, there
must be a least common denominator. Right now, sockets appears to be
the least common demoninator. It is not pretty, but it works.

Besides, the awkward style provides a certain amount of job security (8-)).


Bill VerSteeg
Network Research Corp
bvs@nrc.com
-- 
Bill VerSteeg
internet	bvs@nrc.com
UUCP		gatech.edu!galbp!bagend!bvsatl!bvs