blob: f7bbc2d70bc29e1cd45ba2df7a092e4d7bef031f (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
// $Id$
The following TAO applications illustate various Portable Object
Adapter (POA) interfaces and their usage scenarios.
Individual README files in the respective directories explain
these applications further.
. RootPOA
This example explains how to obtain the name of the
RootPOA.
. NewPOA
This example explains the operations involved in
creation of new POAs.
. FindPOA
This example explains registering an adapter activator
for a POA and also the find_POA operation.
. Generic_Servant
A simple interface (Foo) is defined here and its
implementations, server and client programs are
available, which can be used for testing POA
applications. Several servers for that interface are
implemented using different POA policies; a common
client for all the servers is also provided.
. On_Demand_Activation
Contains programs that test the POA's 2 types of
activation of objects on demand, namely , Servant
Activator approach and Servant Locator , which depend
on the RETAIN/NON-RETAIN policy of a POA.
. Default_Servant
Contains a File IDL module and its implementation and
a server,client to test the File Module interfaces.
The System interface uses the USE_DEFAULT_MANAGER policy
to create a POA and registers a single File Descriptor
object as the default servant. The default servant serves
requests for many Descriptor objects.
. Explicit_Activation
This application explains various operations involved
in the explicit activation of objects; including the
creation of objects without servants (the servant is
created on demand). NOTE: Currently the example does
not work. < It compiles; but at runtime, _narrow()
raises an exception on the client. >
|