Legacy Issue Number: 3937
Source: Open Networks Engineering ( Jean-Christophe Dubois)
I found 2 (possibly) contradictory statement in 99-10-04 for "emits" ports.
1) in 126.96.36.199 The Event Interface
EventConsumerBase obtain_channel (in string supp_name, in EventHeader hdr)
The obtain_channel operation is used by the component to obtain an
EventConsumerBase which it can use to push events. This operation
corresponds to an emits declaration in component IDL. The supp_name string
identifies an Interoperable Naming Service (INS) name which is used to
identify the SupplierAdmin to be used by CORBA notification. The name is
associated with the SupplierAdmin thorough container specific configuration
data. The obtain_channel operation may optionally specify the EventHeader
required by CORBA notification which will be used for all events pushed to
this channel. If hdr is present, it is prefixed to all events pushed to this
channel. If not, it is defaulted as described in Section 66.4, "Event
Management Integration," on page 66-252. If the supp_name is not recognized,
the InvalidName exception shall be raised.
2) in 66.4.2 Transmitting an event
. channel lookup - for emitted events, this is the channel configured for
general use at container start-up, for published events, this is the channel
established by the container for the purpose of pushing this event type.
Section 188.8.131.52 seems to imply that there can be a different event channels
for each emit port while 66.4.2 seems to imply that there is only one event
channel shared by all emits ports.
What means "general use"?
What is the truth/intent?.
Could you make things clear?
I certainly preffer 1)
Reported: CORBA 2.4 — Thu, 5 Oct 2000 04:00 GMT
Disposition: Resolved — CORBA 2.6.1
Updated: Fri, 6 Mar 2015 20:58 GMT