1 - 2 - 3 - 4 - 6 - 8 - A - B - C - D - E - F - G - H - I - J - K - L - M - N - O - P - Q - R - S - T - U - V - W - X
RPC
Click on the red underlined text to get to the source
... VMTP) is a transport
protocol designed to support remote procedure call (RPC) and general
transaction-oriented communication. By transaction-oriented
...
... Poor RPC Performance ...
... First, current protocols provide poor performance for remote procedure
call (RPC) and network file access. This is attributable to three key
causes:
...
...
- TCP requires excessive packets for RPC, especially for
isolated calls. In particular, connection setup and clear
...
... packet loss in a
high-performance RPC environment and, with the increasing
performance of networks ...
... .)
VMTP is designed for ease of implementation and efficient RPC. In
addition, it provides selective retransmission with rate-based flow ...
... VMTP is designed with the next generation of communication
systems in mind. These communication systems are characterized as
follows. RPC, page-level file access and other request-response
behavior dominates. In addition, the communication substrate, both
...
... Figure 1-1: Relation to Other Protocols
The RPC presentation level is not currently defined in the Internet
suite of protocols. Appendix II defines a proposed RPC ...
... RPC presentation level is not currently defined in the Internet
suite of protocols. Appendix II defines a proposed RPC presentation
level for use with VMTP and assumed for the definition of the VMTP ...
... remaining issues and expected directions for the future. Appendix I
lists some standard Response codes. Appendix II describes the RPC
presentation protocol proposed for VMTP and used with the VMTP ...
... management
mechanism that is accessed through a procedural interface (RPC)
implemented on top of VMTP. In particular, information about a remote
entity ...
... application-specified.
The MsgDelivery field is optionally used by the RPC or user level to
specify the portions of the segment data to transmit and on reception,
...
... module as well as for
VMTP modules to communicate this use among themselves. The use of these
options is generally fixed for each remote procedure so that an RPC
mechanism using VMTP can treat the Flags as an integral part of the
...
... authorization on the Request. Describing this situation in the context
of RPC, a nested remote procedure call may be the last action in the
remote procedure and the return parameters are exactly those of the
...
... field if a Request and the Server field if a Response. The
sender and receiver of a message are required to agree in some higher
level protocol (such as an RPC presentation protocol) on who does
further swapping of the MCB and data segment if required by the types of
...
... version of the protocol is similar to that
described by Birrell [1] for secure RPC. The use of runs of packet
groups is similar to Fletcher and Watson's delta-T protocol [10]. The
...
... D.R. Cheriton, "Exploiting Recursion to Simplify an RPC Communication Architecture", in preparation, 1988. ...
... segment data is null and the SegmentSize field is
not used by VMTP and available for user- or RPC-level
uses.
...
... segment data
blocks that were actually received before the message
control block is passed to the user or RPC level. In
particular, the kernel does not discard the packet group
...
... For complete generality, the mapping of the procedures and the
parameters onto VMTP messages should be defined by a RPC presentation
protocol. In the absence of an accepted standard protocol, we define an
RPC presentation protocol for ...
... messages should be defined by a RPC presentation
protocol. In the absence of an accepted standard protocol, we define an
RPC presentation protocol for VMTP as follows.
...
... the return "count" parameter indicates the number of
queued message allowed. Alternatively, the "flags"
parameters indicates the RPC thread service model, in
which case "count" threads are requested, each with an
...
... LocalClientLink and RemoteClientLink (not shown) in the CSR for the
LocalClient and RemoteClient fields, respectively. Note that a CSR
representing an RPC request has both a local and remote entity
...