blob: 4543a24df3a98bb21091bb20aef7d74e860f976a (
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
|
This is the cubit example that uses the TAO IDL compiler to generate
the stubs and skeletons. Additional features include presence of a
factory to create Cubit objects and testing the _bind call to get the
factory object reference.
You can either run the server in the background in the same window as
the client or open a separate window for the client and server.
server:
-------
% svr [-d] [-ORBhost <serverhost>] [-ORBport <portnum>]
[-n <number-of-cubit-objects>]
The server cubit factory maintained num_of_cubit objects (default =
1). They are assigned keys that look like "key0", "key1", ...
When the server is started and you have used the -d flag, you should
see as the first line of output something that looks like
iiop:1.0//swarm:10015/Persistent/886013035/850128/RootPOA/RootPOA_is_BAD/factory
(-ORBobjrefstyle url)
or
IOR:000000000000001649444c3a43756269745...
(-ORBobjrefstyle ior)
Using -d turns on debugging messages. It is additive, i.e., the more
-d options provided, the more debugging you can get. At the moment,
only 2 levels of debugging are implemented, and more than 2 -d options
are ignored.
You need to set -d to get the IOR
client:
-------
% clnt [-d] <-f IOR> -n <iterations>
where IOR is the factory IOR obtained from the server.
|
