1CosEventChannelAdmin(3)    Erlang Module Definition    CosEventChannelAdmin(3)
2
3
4

NAME

6       CosEventChannelAdmin  - The CosEventChannelAdmin defines a set if event
7       service interfaces that  enables decoupled  asynchronous  communication
8       between  objects  and  implements  generic (untyped) version of the OMG
9       COSS standard event service.
10

DESCRIPTION

12       The event service defines two roles for objects: the supplier role  and
13       the consumer role. Suppliers supply event data to the event channel and
14       consumers receive event data from the channel. Suppliers do not need to
15       know  the identity of the consumers, and vice versa. Consumers and sup‐
16       pliers are connected to the event channel via proxies, which  are  man‐
17       aged by ConsumerAdmin and SupplierAdmin objects.
18
19       There are four general models of communication. These are:
20
21         * The canonical push model. It allows the suppliers of events to ini‐
22           tiate the transfer of event data to consumers. Event channels  play
23           the  role  of  Notifier. Active suppliers use event channel to push
24           data to passive consumers registered with the event channel.
25
26         * The canonical pull model. It allows  consumers  to  request  events
27           from  suppliers. Event channels play the role of Procure since they
28           procure events on behalf of consumers. Active consumers can explic‐
29           itly pull data from passive suppliers via the event channels.
30
31         * The  hybrid  push/pull  model.  It  allows consumers request events
32           queued at a channel by suppliers. Event channels play the  role  of
33           Queue.  Active  consumers  explicitly pull data deposited by active
34           suppliers via the event channels.
35
36         * The hybrid pull/push model. It allows the channel  to  pull  events
37           from  suppliers and push them to consumers. Event channels play the
38           role of Intelligent agent. Active event channels can pull data from
39           passive suppliers to push it to passive consumers.
40
41       To  get  access to all definitions, e.g., exceptions, include necessary
42       hrl files by using:
43       -include_lib("cosEvent/include/*.hrl").
44
45       There are seven different interfaces supported in the service:
46
47         * ProxyPushConsumer
48
49         * ProxyPullSupplier
50
51         * ProxyPullConsumer
52
53         * ProxyPushSupplier
54
55         * ConsumerAdmin
56
57         * SupplierAdmin
58
59         * EventChannel
60
61Ericsson AB                     cosEvent 2.2.2         CosEventChannelAdmin(3)