Getting started (universal TCP/IP samples)


Hal Peterson (hrp%fermi.CRAY.COM@uc.msc.umn.edu)
Sun, 12 Jun 88 17:08:44 CDT


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



This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:42:30 GMT