[omniORB] omniEvents & omniNotify and event factories

[Paul Nader]

Hi Jon,

EventChannelAdmin.idl defines an interface called EventChannelFactory that is
a factory for creating channels. It is based on the generic factory defined in the
CosLifeCycle spec.

The example eventc.cc shoes how to create event channels by requesting
the EventChannelFactory.

All other examples (pullcons.cc, pushsupp.cc, etc) illustrate how pull/push
consumers/subscribers connect, disconnect , push, pull, etc to the event channel.

Also note that the Event Service Specification does not require an event channel
factory to be provided by an implementation (ie how channels are created is left
unspecified), although omniEvents does.

Regards, Paul.

jon@totient.demon.co.uk wrote:

> Hi
>
> I've been looking at the omniEvent and omniNotify.
>
> One thing that confuses me is that the Notification service appears to
> come with a factory for creating Event Channels, whereas the event
> service does not.
>
> Using Notification, this means process A could send event to a channel X which are picked
> up by process B. The channel could be created by an independent process
> Z using the EventChannelFactory::create_channel operation
>
> However under omniEvents / Event Service , there does not seem to be
> a factory for creating channels? You have to connect to the channel
> via a proxy.
>
> What I would like to do is have an administrative process which can
> just create Event Channels for use in the Event service.
> Then the push/pull consumer/subscriber could connect and use that
> channel? Or if you want to do that, do you have to use a notification service?
>
> Jon