Erlang -- CosEventChannelAdmin

cosEvent

Reference Manual

Version 2.2.2

- User's Guide
- Reference Manual
- Release Notes
- PDF
- Top

- Expand All
- Contract All

### Table of Contents

- cosEventApp
  - Top of manual page
  - install/0
  - start/0
  - start_channel/0
  - start_channel/1
  - start_channel_link/0
  - start_channel_link/1
  - stop/0
  - stop_channel/1
  - uninstall/0
- CosEventChannelAdmin
- CosEventChannelAdmin_ConsumerAdmin
  - Top of manual page
  - obtain_pull_supplier/1
  - obtain_push_supplier/1
- CosEventChannelAdmin_SupplierAdmin
  - Top of manual page
  - obtain_pull_consumer/1
  - obtain_push_consumer/1
- CosEventChannelAdmin_EventChannel
  - Top of manual page
  - destroy/1
  - for_consumers/1
  - for_suppliers/1
- CosEventChannelAdmin_ProxyPullConsumer
  - Top of manual page
  - connect_pull_supplier/2
  - disconnect_pull_consumer/1
- CosEventChannelAdmin_ProxyPushConsumer
  - Top of manual page
  - connect_push_supplier/2
  - disconnect_push_consumer/1
  - push/2
- CosEventChannelAdmin_ProxyPullSupplier
  - Top of manual page
  - connect_pull_consumer/2
  - disconnect_pull_supplier/1
  - pull/1
  - try_pull/1
- CosEventChannelAdmin_ProxyPushSupplier
  - Top of manual page
  - connect_push_consumer/2
  - disconnect_push_supplier/1

# CosEventChannelAdmin

### Module

CosEventChannelAdmin

### Module Summary

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

### Description

The event service defines two roles for objects: the supplier role and the consumer role. Suppliers supply event data to the event channel and consumers receive event data from the channel. Suppliers do not need to know the identity of the consumers, and vice versa. Consumers and suppliers are connected to the event channel via proxies, which are managed by ConsumerAdmin and SupplierAdmin objects.

There are four general models of communication. These are:

- The canonical push model. It allows the suppliers of events to initiate the transfer of event data to consumers. Event channels play the role of Notifier. Active suppliers use event channel to push data to passive consumers registered with the event channel.
- The canonical pull model. It allows consumers to request events from suppliers. Event channels play the role of Procure since they procure events on behalf of consumers. Active consumers can explicitly pull data from passive suppliers via the event channels.
- The hybrid push/pull model. It allows consumers request events queued at a channel by suppliers. Event channels play the role of Queue. Active consumers explicitly pull data deposited by active suppliers via the event channels.
- The hybrid pull/push model. It allows the channel to pull events from suppliers and push them to consumers. Event channels play the role of Intelligent agent. Active event channels can pull data from passive suppliers to push it to passive consumers.

To get access to all definitions, e.g., exceptions, include necessary hrl files by using:
-include_lib("cosEvent/include/*.hrl").

There are seven different interfaces supported in the service:

- ProxyPushConsumer
- ProxyPullSupplier
- ProxyPullConsumer
- ProxyPushSupplier
- ConsumerAdmin
- SupplierAdmin
- EventChannel