🚀 go-pugleaf

Programming at the RPC level is a good way to isolate yourself from
the underlying TLI/socket and transport issues you may not care about.

OSF/DCE's RPC supports a number of transports and connection schemes,
including sockets.  They are moving to support TLI from what I'm told.

The old well-known Sun RPC (ONC version 4.0) is basically
sockets-only.  It allows one to easily mix-in the IPCs you like best,
performing IPCs or RPCs across the network, on the same machine or even
the same process with little XDR penalty (esp. if your machine already
things in network order bytes, e.g., a SPARC).

The newer Solaris-era TI-RPC is a superset, with backward compat. to
ONC 4.0.  It adds transport independence (built on TLI) in a clever,
run-time or compile-time fashion.  If you continue to require socket fd
fiddling (e.g., within X11), you need to plan this in.

You've got to start thinking about name serving instead of ports.
These daemons must be running too.  All three RPC systems are
available now.  The last two can be downloaded for free (although I bet
you already have the 4.0 development tools).  There are other RPC
systems as well.


John J. Bloomer (issuing my opinions, not those of GE or O'Reilly and Assoc.)
KWC317, General Electric Corporate Research and Development
PO Box 8, Schenectady NY 12301
-- 
John J. Bloomer 518-387-6964 (dialcomm 833) FAX -7332
KWC317, General Electric Corporate Research and Development
PO Box 8, Schenectady NY 12301