🚀 go-pugleaf

In article <1197@pivot-sts.sbi.com> ken@comanche.sbi.com (Ken Jones - Consultant) writes:
	We have been building distributed systems on Wall Street for 4
	years and abandonded RPC's as unreliable. In tests of heavily
	loaded systems, RPC's will fail to be delievered.  Therefore,
	we have switched to using TCP/IP connections with XDR streams
	on top.  In thus doing so we have developed a client/server
	commericial product with a simple API and client lib's for C
	and X-Windows programs.

I don't get it.  If you create your CLIENT with clnttcp_create(), then
RPC _IS_ TCP/IP connections with XDR streams on top.  How could
clnttcp_create be less reliable than your own version of the same
thing?

	The possible system wide overhead of a sustained TCP/IP
	connection far outweighs the benifits of reliable communication
	across subnets.

You must mean the benefits outweigh the overhead.  If you believed the
opposite, you wouldn't be using TCP/IP, right?

	We would urge any group NOT to use RPC's in developing
	distributed systems since they fail at the worst possible
	time.

You must be using clntudp_create and a UDP connection.  That would be
unreliable.
-- 
Greg Holmberg

Third Eye Software, Inc.                415/321-0967 Voice
750 Menlo Avenue, Suite 300             415/321-2066 Fax