Foreword |
|
xvii | |
Acknowledgments |
|
xix | |
|
|
1 | (12) |
|
|
1 | (1) |
|
Why Architecture Is Important |
|
|
2 | (2) |
|
Distributed Architectures |
|
|
4 | (1) |
|
|
5 | (2) |
|
|
7 | (1) |
|
|
8 | (1) |
|
|
8 | (3) |
|
|
9 | (1) |
|
Partitioning, Interfaces, and Granularity |
|
|
9 | (1) |
|
|
9 | (1) |
|
Life Cycle and Persistence |
|
|
9 | (1) |
|
|
10 | (1) |
|
|
10 | (1) |
|
|
10 | (1) |
|
Architecture Considerations for Deployment |
|
|
10 | (1) |
|
Appendix: COM/CORBA Integration |
|
|
10 | (1) |
|
|
11 | (2) |
|
|
13 | (24) |
|
Quick Review of Object-Oriented Concepts |
|
|
13 | (5) |
|
Objects, Classes, and inheritance |
|
|
14 | (2) |
|
|
16 | (1) |
|
|
16 | (1) |
|
|
16 | (2) |
|
Object Based Distribution |
|
|
18 | (2) |
|
|
20 | (5) |
|
|
21 | (1) |
|
|
22 | (1) |
|
|
23 | (1) |
|
|
23 | (2) |
|
What CORBA Does Not Provide |
|
|
25 | (5) |
|
|
25 | (3) |
|
Interoperable naming service |
|
|
28 | (1) |
|
|
28 | (1) |
|
|
29 | (1) |
|
|
29 | (1) |
|
|
30 | (1) |
|
Service-Oriented Architecture |
|
|
30 | (1) |
|
Integration Strategies with Existing Systems |
|
|
31 | (6) |
|
Integration strategy for a database |
|
|
33 | (1) |
|
Integration strategy for a library |
|
|
34 | (1) |
|
Integration strategy for an application |
|
|
34 | (1) |
|
|
35 | (1) |
|
|
36 | (1) |
|
|
36 | (1) |
|
Partitioning, Interfaces, and Granularity |
|
|
37 | (30) |
|
|
38 | (1) |
|
|
39 | (2) |
|
|
41 | (6) |
|
|
42 | (2) |
|
|
44 | (2) |
|
|
46 | (1) |
|
|
47 | (1) |
|
|
47 | (4) |
|
|
48 | (2) |
|
Granularity and performance |
|
|
50 | (1) |
|
Example: Document Retrieval |
|
|
51 | (13) |
|
|
51 | (3) |
|
|
54 | (2) |
|
Initial Interface Definition |
|
|
56 | (4) |
|
|
60 | (4) |
|
|
64 | (1) |
|
|
65 | (2) |
|
|
67 | (30) |
|
Examples of Using Meta-Information |
|
|
68 | (2) |
|
|
68 | (2) |
|
|
70 | (1) |
|
Meta-Information in CORBA |
|
|
70 | (24) |
|
|
71 | (7) |
|
Implementation Repository |
|
|
78 | (1) |
|
|
79 | (5) |
|
Dynamic Interface Invocation |
|
|
84 | (5) |
|
Dynamic Skeleton Interface |
|
|
89 | (2) |
|
|
91 | (1) |
|
|
92 | (2) |
|
|
94 | (1) |
|
|
94 | (1) |
|
|
95 | (2) |
|
Life Cycle And Persistence |
|
|
97 | (28) |
|
|
98 | (8) |
|
Life cycle support implementations |
|
|
99 | (7) |
|
Distributed Object Life Cycle |
|
|
106 | (6) |
|
|
106 | (6) |
|
|
112 | (10) |
|
Know when to save, know when to load |
|
|
113 | (1) |
|
Knowing how to save and load |
|
|
114 | (1) |
|
|
115 | (1) |
|
|
116 | (1) |
|
|
117 | (1) |
|
|
118 | (2) |
|
|
120 | (1) |
|
|
121 | (1) |
|
|
121 | (1) |
|
|
122 | (1) |
|
|
123 | (1) |
|
|
123 | (2) |
|
|
125 | (36) |
|
|
126 | (12) |
|
|
127 | (1) |
|
Database systems and TP monitors |
|
|
128 | (2) |
|
|
130 | (1) |
|
|
131 | (1) |
|
|
132 | (1) |
|
|
133 | (1) |
|
|
134 | (1) |
|
|
135 | (3) |
|
The OMG Object Transaction Service |
|
|
138 | (17) |
|
|
139 | (1) |
|
Basic OTS programming model |
|
|
140 | (1) |
|
|
141 | (2) |
|
|
143 | (1) |
|
Transaction context propagation |
|
|
143 | (1) |
|
|
144 | (1) |
|
|
144 | (1) |
|
|
145 | (5) |
|
|
150 | (2) |
|
|
152 | (1) |
|
Example: transactional document management |
|
|
152 | (3) |
|
Concurrency Control Service |
|
|
155 | (4) |
|
|
155 | (2) |
|
|
157 | (2) |
|
|
159 | (1) |
|
|
160 | (1) |
|
|
160 | (1) |
|
|
161 | (32) |
|
|
162 | (6) |
|
|
162 | (1) |
|
|
163 | (2) |
|
Security functionality (features) |
|
|
165 | (1) |
|
Developing a security policy |
|
|
166 | (2) |
|
Review of the OMG Security Service |
|
|
168 | (22) |
|
|
172 | (3) |
|
Principals, authentication, and credentials |
|
|
175 | (4) |
|
|
179 | (1) |
|
|
179 | (4) |
|
|
183 | (2) |
|
Authorization/access control |
|
|
185 | (1) |
|
Privacy and integrity of messages |
|
|
186 | (1) |
|
|
186 | (1) |
|
|
187 | (2) |
|
Security interoperability |
|
|
189 | (1) |
|
|
190 | (1) |
|
|
191 | (1) |
|
|
192 | (1) |
|
|
192 | (1) |
|
|
193 | (24) |
|
|
193 | (9) |
|
|
194 | (2) |
|
|
196 | (6) |
|
|
202 | (7) |
|
|
203 | (1) |
|
|
203 | (2) |
|
|
205 | (1) |
|
|
206 | (1) |
|
|
207 | (2) |
|
|
209 | (1) |
|
|
210 | (5) |
|
|
210 | (3) |
|
How XML fits in with CORBA |
|
|
213 | (2) |
|
|
215 | (1) |
|
|
216 | (1) |
|
Architecture Considerations for Deployment |
|
|
217 | (30) |
|
|
217 | (2) |
|
|
219 | (10) |
|
|
220 | (3) |
|
|
223 | (5) |
|
|
228 | (1) |
|
|
229 | (4) |
|
|
229 | (1) |
|
|
230 | (1) |
|
|
231 | (2) |
|
|
233 | (13) |
|
|
233 | (1) |
|
|
234 | (1) |
|
|
235 | (1) |
|
|
235 | (1) |
|
|
235 | (1) |
|
|
236 | (1) |
|
Balancing by Naming Service |
|
|
237 | (2) |
|
|
239 | (1) |
|
Naming Service/OAD summary |
|
|
240 | (1) |
|
|
240 | (6) |
|
|
246 | (1) |
Appendix: COM/CORBA Integration |
|
247 | (20) |
|
|
247 | (1) |
|
|
248 | (1) |
|
|
248 | (1) |
|
|
249 | (1) |
|
|
250 | (7) |
|
Object life cycle and identity |
|
|
251 | (2) |
|
Interface and interface identity |
|
|
253 | (1) |
|
|
254 | (2) |
|
|
256 | (1) |
|
|
257 | (1) |
|
|
257 | (5) |
|
|
258 | (1) |
|
|
258 | (1) |
|
|
258 | (4) |
|
|
262 | (2) |
|
COM and Automation objects from CORBA clients |
|
|
262 | (1) |
|
CORBA objects from COM and Automation clients |
|
|
263 | (1) |
|
|
264 | (1) |
|
|
264 | (1) |
|
|
265 | (2) |
Index |
|
267 | |