From 088f0784a3b785a68685de27d1acf297a1d65dc2 Mon Sep 17 00:00:00 2001 From: John Terpstra Date: Tue, 28 Jun 2005 23:46:37 +0000 Subject: Update. (This used to be commit 9d0431b8980e1b918d7d87af4191d6173a63baf9) --- docs/Samba3-HOWTO/TOSHARG-glossary.xml | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) (limited to 'docs/Samba3-HOWTO') diff --git a/docs/Samba3-HOWTO/TOSHARG-glossary.xml b/docs/Samba3-HOWTO/TOSHARG-glossary.xml index 2521f6c9f0..aa069864cf 100644 --- a/docs/Samba3-HOWTO/TOSHARG-glossary.xml +++ b/docs/Samba3-HOWTO/TOSHARG-glossary.xml @@ -13,7 +13,7 @@ - Active Directory Service + Active Directory Service ADS A service unique to Microsoft Windows 200x servers that provides a centrally managed @@ -202,6 +202,23 @@ + + Remote Procedure Call + RPC + + 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 programatic a 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. + + + Server Message Block SMB -- cgit