-
Notifications
You must be signed in to change notification settings - Fork 7
/
CHANGES_201
120 lines (81 loc) · 4.41 KB
/
CHANGES_201
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
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
Release Notes for 2.0.1 (15th January 2000)
=======================
This release is a minor release which fixes a number of bugs in
omniEvents 2.0.0. This release adds support for multiple
SupplierAdmin and ConsumerAdmin objects per event channel. To
re-use your existing persistence log files you will need to
modify them as described in sections 1 & 3 below.
Also, as from this release omniEvents is supplied in a single
library in both static and dynamic versions.
The last release of omniEvents was 2.0.0 (20th Nov 1999). The
previous major release was 1.0.3 (11th May 1999).
The source code distribution for omniEvents 2.0.1 is available at :
http://www.uk.research.att.com/omniORB/contribapp.html#omniEvents
Changes since 2.0.0
-------------------
1. Support for multiple Admin objects per event channel.
omniEvents now creates by default new supplierAdmin and consumerAdmin
objects each time the for_suppliers() and for_consumers() methods are
called on an EventChannel_i interface. This change has been introduced
to more closely align omniEvents with the Notification Service to allow
for the eventual implementation of QOS parameters and filters at the
Admin object level.
If you wish to re-use your existing persistence log files you will
need to make some minor changes to them as described below. The files
you should modify are located in the $OMNIEVENTS_LOGDIR and are named:
omnievents-<hostname>.log and
omnievents-<hostname>.bak
1.1 Delete all instances of COMMON and channelFactory but the last in
each file.
1.2 Move each end every instance of pxyPullSupplier and pxyPushSupplier
into the corresponding consumerAdmin instance immediatly above it.
1.3 Move each end every instance of pxyPullConsumer and pxyPushConsumer
into the corresponding supplierAdmin instance immediatly above it.
Notes:
- You don't need to re-indent the lines you move.
- Make sure you delete/move the entire instance (i.e including the start
and closing braces - and everything else in between).
2. Restructured the containment of Proxies.
The proxies for suppliers and consumers are no longer contained
directly under the event channel. Instead they are located under
the corresponding SupplierAdmin or ConsumerAdmin object initialy
used to create them.
3. Removed factory dependency on naming service.
The EventChannelFactory_i class no longer persists its name or hence
bind itself with the naming service when restarted from persistency. The
default factory created by the omniEvents executable is still bound to
the naming service by the omniEvents executable (as was done prevously)
but it is no longer re-bound during re-starts.
If you wish to re-use your existing persistence log files you will
need to make some minor changes to them as described below. The files
you should modify are located in the $OMNIEVENTS_LOGDIR and are named:
omnievents-<hostname>.log and
omnievents-<hostname>.bak
3.1 Delete all instances of COMMON and channelFactory but the last in
each file.
3.2 Move the port entry in the instance of COMMON into the channelFactory
instance.
3.3 Delete the entire instance of COMMON.
Notes:
- You don't need to re-indent the line.
4. Examples no longer compiled with omniEvents libraries.
The examples provided are no longer compiled using the omniEvents
libraries but with the generated stubs instead. This is to re-enforce
the fact that they are not dependent on omniEvents.
5. Bugs fixed.
- Push Suppliers can now be connected to a ProxyPushConsumer using a nil
reference. The ProxyPushConsumer_i::connect_push_supplier() method has
been changed to allow a nil parameter to be passed and no longer throws
a CORBA::BAD_PARAM exception.
- Pull Consumers can now be connected to a ProxyPullSupplier using a nil
reference. The ProxyPullSupplier_i::connect_pull_consumer() method has
been changed to allow a nil parameter to be passed and no longer throws
a CORBA::BAD_PARAM exception.
- Fixed memory leak when persisting connected proxies. Failed to delete
stringified IOR.
- Fixed broken persistency during restart. omniEvents failed to re-open
logfile.
- Removed requirement for extern usage() function from omniEventsLog.
- Removed inclusion of CosLifeCycle.idl in CosEventChannelAdmin.idl.
- Modified pull model thread signaling to use counting semaphores to
avoid missing pull requests.