Method used to communicate between computers using the Internet. The network layer dealing with RPCs is the session layer. It is one layer further removed from hardware dependancies then the transport (TCP/IP, sockets) layer.
(RPC) A protocol governing the method with which an application activates processes on other nodes & retrieves the results.
Calls built by clients and executed on servers with results returned to the client across the network; protocol allows applications to call subroutines physically located in a different part of the network.
(n.) a structured implementation of a client-server interaction.
Remote Procedure Call (RPC) is a generic term for a procedure call between two systems. Although the two systems may be on the same machine, RPC usually refers to procedure calls across a network – one machine makes a procedure call, and the system bundles the call together with all the necessary communications code and sends it to another machine on the network for execution. The idea is to provide a simple mechanism for creating cooperative processing applications. There is no true RPC mechanism within SNA, although APPC provides all the technical infrastructure to build one. The IBM-backed OSF has attempted to create a standard for RPCs in the Unix environment, and it’s distinctly possible that this will be used as a model for other standards. See also APPC/MVS.
In programming, a call by one program to a second program on a remote system. The second program usually performs a task and returns the results of that task to the first program.
An API that supports the ability for application programs running on one computer to make program calls to execute procedures or access data on another networked computer. With the RPC API, the RPC client is the application program making the request and the RPC server is the application program that executes that request.
a call from Outlook to the Exchange Server, asking Exchange Server to perform a task and return the results to Outlook
an interprocess communication technique which allows client/server software to communicate
a request made by a process in one computer to another computer across a network
a way of abstracting the procedure call of programs across process boundaries using network protocols
A protocol that allows a program on a client computer to run a program on a server.
A means of communication between two tasks running on separate machines linked by a LAN. One machine can request a service, typically computation, from the other, by executing a high level request known as a language procedure call. RPCs are an underlying architectural element of distributed processing and client/server computing.
Executing what looks like a normal procedure call (or method invocation) by sending network packets to some remote host.
Standard protocol for client/server communication; a routine that transfers functions and data between client and server processes.
A procedure executed on a different Adaptive Server from the Adaptive Server the user is logged into.
A protocol through which applications receive information over a network without explicit knowledge of the network.
A protocol used in the client-server model that allows one application (the client) to request a service from another application (the server) located on another computer in a network without having to understand network details.
A procedure executed on a different SQL Server from the SQL Server the user is logged into.
A process (API) by which a client instructs a server (or DBMS) to execute a program routine. "A facility for embedding subroutine calls within an application on one [ ] system, which then invokes execution of a routine residing on another [ ] system. The systems pass parameters to communicate the specifications of the necessary processing." "A mechanism that extends the notion of local procedure call to a fully distributed computing environment, enabling an application to be distributed among multiple systems in a way that is highly transparent to the application-level code."
This protocol allows the construction of client-server applications using a demand/response protocol with management of transactions. The client is blocked until a response is returned from the server, or a user-defined optional timeout occurs. RPC guarantees at-most-once semantics for the delivery of the request. See also inter-process communication (IPC), and asynchronous communication mode.
A message-passing facility that allows a distributed program to call services available on various computers in a network. Used during remote administration of computers, RPC provides a procedural view, rather than a transport-centered view, of networked operations.
A method a program can use to make a call to another program across a network without specifically dealing with network protocols. It is often used for...
a protocol that one program can use to request a service from a program located in another computer in a network without having to understand network details.
A mechanism used to invoke functions that are not locally available to a process; typically used for implementing server calls from a client.
remote procedure call (RPC) - A communication mechanism that allows computers to communicate with one another over a network. An RPC consists of a procedure identifier, parameters passed to the procedure, and a value returned to the caller (client computer) after the procedure has executed on the remote system (server computer).
RPCs are a means for executing network operations. The RPC protocol is independent of transport protocols. RPC does not try to implement any kind of reliability and the application that uses RPCs must be aware of the type of transport protocol underneath RPC. An RPC is like a programmatic jump subroutine over a network. RPCs used in the UNIX environment are specified in RFC 1050. RPC is a powerful technique for constructing distributed, client-server based applications. It is based on extending the notion of conventional, or local procedure calling, so that the called procedure need not exist in the same address space as the calling procedure. The two processes may be on the same system, or they may be on different systems with a network connecting them. By using RPC, programmers of distributed applications avoid the details of the interface with the network. The transport independence of RPC isolates the application from the physical and logical elements of the data communications mechanism and allows the application to use a variety of transports.
An extension of the paradigm of a "local" procedure call that enables a client application to invoke a procedure in a remote (server) application as if the remote procedure were resident on the local machine. RPCs distribute application execution.
This is a protocol that one application can use to request a service from another application located on another computer in a network without having to understand the specific network details. It can also be used to build a small application module or applet for use as part of a Web page. Applets make it possible for a Web page user to interact with the page.
A TCP/IP protocol that provides a routine to call a server, which returns output and status (return) codes to the client.
A standard protocol for client-server communication.
A programming interface that allows one program to use the services of another program located in a remote application system.
A message-passing facility that is independent of the underlying network and allows a distributed application to call services available on various computers in a network. Microsoft Exchange Server uses RPC for client-server communications.
A message-passing facility that allows a distributed application to call services that are available on various computers on a network. Used during remote administration of computers. See also: service
An easy and popular paradigm for implementing the client-servermodel of distributed computing. In general, a request is sent toa remote system to execute a designated procedure, using argumentssupplied, and the result returned to the caller. There are manyvariations and subtleties in various implementations, resulting ina variety of different (incompatible) RPC protocols.[Source: RFC1208] repeater
A protocol which allows a program running on one host to cause code to be executed on another host without the programmer needing to explicitly code for this. RPC is an easy and popular paradigm for implementing the client-server model of distributed computing. An RPC is implemented by sending request message to a remote system (the server) to execute a designated procedure, using arguments supplied, and a result message returned to the caller (the client).
Remote procedure call (RPC) is a technology that allows a computer program to cause a subroutine or procedure to execute in another address space (commonly on another computer) without the programmer explicitly coding the details for this remote interaction. That is, the programmer would write essentially the same code whether the subroutine is local to the executing program, or remote. When the software in question is written using object-oriented principles, RPC may be referred to as remote invocation or remote method invocation.