🚀 go-pugleaf

In article <7201@transfer.stratus.com> cme@ellisun.sw.stratus.com (Carl Ellison) writes:
>...
>The good point is that it's easy to program -- nothing new -- just the same
>old procedure calls.

This is mostly true.  The network interface can add complications in
the form of exceptions which would not be their in the straightup
procedure call environment.

>The bad point is that while the callee is doing its thing *and* while that
>call is being transmitted *and* while the reply is coming back, the caller
>is twiddling its thumbs -- either literally spinning or doing a task
>switch. 

I'm not sure how ONC handles this but in DCE threads are used so that
the entire process need not block.  When you use threads with rpcs you
effectively blur the line between client and server at the process
level.  For example, in our first DCE based application each user
interface process was both a client of the database server and a
server itself which exported an interface used for asynchronous
message passing between users.  It's possible for one of these
processes to be issuing calls to the database server while servcing
it's own interface simultaneously.


Best regards,
-- 
Kevin P. Tyson		Phone:  212-657-5928	Fax:    212-657-4599
E-Mail: Kevin_Tyson@fig.citib.com or kpt@iisa.com