| Summary: | The remote operations protocol [X229] is used by one application process to exchange operation information with a remote process. An operation request, with associated parameters, is sent using the Invoke()primitive, and the outcome is returned using the Result(), Error(), or Reject() primitives. ISO defines a stack of protocol layers to support the remote operations protocol. There is redundancy in this stack and services provided by the stack do not closely match the needs of remote operations. Therefore a more suitable supporting protocol is necessary.
A supporting protocol must be efficient in terms of association setup and data transfer, must support both interested and disinterested servers, and must provide only the services required by remote operations. Association setup must be efficient as remote operation associations can be numerous and short lived. Interested servers are common, warranting support, though disinterested servers must not suffer the overhead accompanying this support. Several efficient request/response protocols exist capable of supporting remote operations, though each has disadvantages.
This thesis defines a request/response protocol, RRP, which satisfies the criteria above. RRP requires no separate PDU transfer to establish or release an association. Data transfer is efficient in terms of network utilization, unnecessary retransmissions and acknowledgements. RRP assumes an unsequenced, unreliable, and error prone datagram service. RRP provides a reliable, sequenced, synchronous request/response service. RRP provides optional peer process monitoring for interested servers. === Science, Faculty of === Computer Science, Department of === Graduate
|
|---|
