![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to what.tex CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / cookbook|
Return to what.tex CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / isode-beta / doc / cookbook |
1.1 root 1: % -*- LaTeX -*- (really SLiTeX)
2:
3: \begin{bwslide}
4: \part {WHAT NOW?}\bf
5:
6: \begin{nrtc}
7: \item COMPARISON TO SUN RPC/XDR
8:
9: \item COMPARISON TO APOLLO NCS
10: \end{nrtc}
11: \end{bwslide}
12:
13:
14: \begin{bwslide}
15: \ctitle {GUIDELINES}
16:
17: \begin{nrtc}
18: \item NOT TRYING TO SAY WHICH IS BETTER
19:
20: \item MERELY TRYING TO COMPARE AND CONTRAST
21:
22: \item REFERENCE DOCUMENT IS USED AS BASELINE\\
23: (SOME INFORMATION MAY BE DATED)
24: \end{nrtc}
25: \end{bwslide}
26:
27:
28: \begin{bwslide}
29: \part* {COMPARISON TO\\ SUN RPC/XDR}\bf
30:
31: \begin{nrtc}
32: \item ALTHOUGH NOT THE FIRST RPC SYSTEM DEPLOYED,
33: CERTAINLY THE FIRST ``POPULARIZATION'' OF AN RPC SYSTEM
34:
35: \item SUN RPC/XDR IS BEST (UN)KNOWN FOR MAKING NFS POSSIBLE
36: \end{nrtc}
37: \end{bwslide}
38:
39:
40: \begin{bwslide}
41: \ctitle {REFERENCE DOCUMENT}
42:
43: \begin{nrtc}
44: \item REMOTE PROCEDURE CALL PROGRAMMING GUIDE
45: \begin{nrtc}
46: \item VERSION: REVISION B OF 17 FEBRUARY 1986
47:
48: \item SOURCE: SMI DOCUMENTATION SET
49: \end{nrtc}
50: \end{nrtc}
51: \end{bwslide}
52:
53:
54: \begin{bwslide}
55: \ctitle {SYNTAX CHARACTERISTICS}
56:
57: \begin{nrtc}
58: \item NO FORMAL ABSTRACT SYNTAX, PER SE
59: \begin{nrtc}
60: \item APPLICATION PROTOCOL DEFINES DATA STRUCTURES EXCHANGED
61:
62: \item INITIALLY, NO STUB COMPILER\\ (THERE IS ONE NOW)
63: \end{nrtc}
64:
65: \item SERIALIZATION METHOD IS CALLED XDR, EXTERNAL DATA REPRESENTATION
66: \begin{nrtc}
67: \item CANONICAL FORM WITH IMPLICIT TAGS
68:
69: \item MOST QUANTITIES PADDED TO 32--BIT BOUNDARIES
70:
71: \item ANY DATA TYPE CAN BE SERIALIZED
72: \end{nrtc}
73: \end{nrtc}
74: \end{bwslide}
75:
76:
77: \begin{bwslide}
78: \ctitle {PROTOCOL CHARACTERISTICS}
79:
80: \begin{nrtc}
81: \item PROTOCOL IS SIMPLE REQUEST/REPLY INTERACTION
82: \begin{nrtc}
83: \item BY CONVENTION, EACH APPLICATION HAS A ``NULL'' PROCEDURE
84: \end{nrtc}
85:
86: \item MULTIPLE TRANSPORT PROTOCOLS SUPPORTED
87: \begin{nrtc}
88: \item ALTHOUGH UDP (DoD USER DATAGRAM PROTOCOL) IS THE MOST COMMON
89:
90: \item THIS IMPACTS, e.g., THE SIZE OF ARGUMENTS THAT CAN BE PASSED
91: IN A REQUEST
92: \end{nrtc}
93:
94: \item SUPPORT FOR BROADCAST MEDIA
95: \end{nrtc}
96: \end{bwslide}
97:
98:
99: \begin{bwslide}
100: \ctitle {BINDING CHARACTERISTICS}
101:
102: \begin{nrtc}
103: \item SERVICE IS IDENTIFIED BY
104: \begin{nrtc}
105: \item PROGRAM NUMBER (32--BITS)
106:
107: \item VERSION NUMBER (32--BITS)
108: \end{nrtc}
109:
110: \item MAPPING OF SERVICE TO NETWORK ADDRESS IS DONE THROUGH PORT MAPPER
111:
112: \item SUPPORT FOR DIFFERENT AUTHENTICATION SCHEMES
113: \end{nrtc}
114: \end{bwslide}
115:
116:
117: \begin{bwslide}
118: \part* {COMPARISON TO\\ APOLLO NCS}\bf
119:
120: \begin{nrtc}
121: \item ANOTHER ENTRY INTO THE POPULAR RPC MARKET
122:
123: \item EMPHASIZES OBJECT-BASED ABSTRACTIONS
124: \end{nrtc}
125: \end{bwslide}
126:
127:
128: \begin{bwslide}
129: \ctitle {REFERENCE DOCUMENT}
130:
131: \begin{nrtc}
132: \item NETWORK COMPUTING SYSTEM: A TECHNICAL OVERVIEW
133: \begin{nrtc}
134: \item VERSION: FEBRUARY 1987 (DOCUMENT 002402--322)
135:
136: \item SOURCE: APOLLO WHITE PAPER
137: \end{nrtc}
138: \end{nrtc}
139: \end{bwslide}
140:
141:
142: \begin{bwslide}
143: \ctitle {SYNTAX CHARACTERISTICS}
144:
145: \begin{nrtc}
146: \item A FORMAL SYNTAX IS USED
147: \begin{nrtc}
148: \item NETWORK INTERFACE DEFINITION LANGUAGE (NIDL)
149:
150: \item ANY DATA TYPE CAN BE DESCRIBED
151:
152: \item NIDL COMPILER PRODUCES ``C'' AND ``PASCAL'' BINDINGS
153: \end{nrtc}
154:
155: \item SERIALIZATION (APOLLO CALLS IT \emph{MARSHALLING}) IS BASED ON THE
156: \begin{nrtc}
157: \item ``RECEIVER MAKES IT RIGHT''
158: \end{nrtc}
159: PRINCIPLE
160: \end{nrtc}
161: \end{bwslide}
162:
163:
164: \begin{bwslide}
165: \ctitle {PROTOCOL CHARACTERISTICS}
166:
167: \begin{nrtc}
168: \item A LIGHTWEIGHT TRANSACTION PROTOCOL IS USED
169: \begin{nrtc}
170: \item CAN DISTINGUISH (NON-)IDEMPOTENT OPERATIONS
171: \end{nrtc}
172:
173: \item MULTIPLE TRANSPORT PROTOCOLS SUPPORTED
174: \begin{nrtc}
175: \item EMPHASIZING USE OF THE BSD SOCKET ABSTRACTION
176: \end{nrtc}
177:
178: \item SUPPORT FOR MULTI-TASKING
179: \end{nrtc}
180: \end{bwslide}
181:
182:
183: \begin{bwslide}
184: \ctitle {BINDING CHARACTERISTICS}
185:
186: \begin{nrtc}
187: \item SERVICE (OBJECT) IS IDENTIFIED BY \emph{UNIQUE ID} OR
188: \emph{INTERFACE NAME}
189: \begin{nrtc}
190: \item REPLICATION AND CONSISTENCY IS CONSIDERED
191: \end{nrtc}
192:
193: \item MAPPING OF SERVICE TO NETWORK ADDRESS IS DONE THROUGH LOCATION BROKER
194:
195: \item SUPPORT FOR DIFFERENT AUTHENTICATION SCHEMES
196:
197: \item SUPPORT FOR AUTHORIZATION PLANNED
198: \end{nrtc}
199: \end{bwslide}
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.