Remote Procedure Call

In computer science, a remote procedure call (RPC) is an inter-process communication that allows a computer program to cause a subroutine or procedure to execute in another address space (commonly on another computer on a shared network) without the programmer explicitly coding the details for this remote interaction. That is, the programmer writes essentially the same code whether the subroutine is local to the executing program, or remote. When the software in question uses object-oriented principles, RPC is called remote invocation or remote method invocation.

Many different (often incompatible) technologies can be used to implement the concept.

Internet protocols
Application layer
  • DHCP
  • DHCPv6
  • DNS
  • FTP
  • HTTP
  • IMAP
  • IRC
  • LDAP
  • MGCP
  • NNTP
  • NTP
  • POP
  • RPC
  • RTP
  • RTSP
  • SIP
  • SMTP
  • SNMP
  • SOCKS
  • SSH
  • Telnet
  • TLS/SSL
  • XMPP
  • (more)
Transport layer
  • TCP
  • UDP
  • DCCP
  • SCTP
  • RSVP
  • (more)
Routing protocols *
  • BGP
  • OSPF
  • RIP
  • (more)
Internet layer
  • IP
    • IPv4
    • IPv6
  • ICMP
  • ICMPv6
  • ECN
  • IGMP
  • IPsec
  • (more)
Link layer
  • ARP/InARP
  • NDP
  • Tunnels
    • L2TP
  • PPP
  • Media access control
    • Ethernet
    • DSL
    • ISDN
    • FDDI
  • (more)
* Not a layer. A routing protocol belongs either to application or network layer.

Read more about Remote Procedure Call:  History and Origins, Message Passing, Other RPC Analogues

Famous quotes containing the words remote and/or call:

    But often the presence of mind and energy of a person remote from the spotlight decide the course of history for centuries to come.
    Stefan Zweig (18811942)

    I do know of these
    That therefore only are reputed wise
    For saying nothing; when I am very sure
    If they should speak, would almost damn those ears
    Which hearing them would call their brothers fools.
    William Shakespeare (1564–1616)