Path: utzoo!attcan!uunet!husc6!mailrus!ames!pasteur!ucbvax!fermi.CRAY.COM!hrp
From: hrp@fermi.CRAY.COM (Hal Peterson)
Newsgroups: comp.protocols.tcp-ip
Subject: Getting started (universal TCP/IP samples)
Message-ID: <8806122208.AA06949@fermi.cray.com>
Date: 12 Jun 88 22:08:44 GMT
References: <159@heart-of-gold>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 14

You ask for a universal sample client/server pair.  The trick is the
``universal'' part, in the face of zillions of hardware architectures,
implementation languages, and interfaces to the protocols and OS.  A
change in any ONE of those three parameters can cause enormous porting
headaches for any non-trivial program.  The best you can do is either
a vague and generic description of, say, the sequence of actions an
ULP must use to handshake with TCP (which you can find in the RFCs) or
a specific example that's reliably good for one kind of box running
one flavor of OS/protocol interface and is written on one source
language.  Neither of those is what you want.


Hal Peterson / Cray Research / 1440 Northland Dr. / Mendota Hts, MN  55120
hrp%hall.CRAY.COM@umn-rei-uc.ARPA	ihnp4!cray!hrp	    (612) 681-3145