Event Service
Summary by Peter Jacobs
Implementation by Tawee Pimsarn
This review of the CORBA Event Service contains a summary and an implementation.
Summary
The OrbixEvents Programmer’s Guide from IONA Technologies PLC was used to prepare this summary.
The guide is available from IONA’s site at http://www.iona.com or by downloading it directly in Adobe Acrobat Reader format.
Summary Contents
- Communicating Indirectly
- Event Transfer And Communication
- Event Example
- Programming Interface
- Untyped Push
- Untyped Pull
- Typed Push
- Typed Pull
Programming Interface
In untyped event communication, an event is propagated by a series of generic push() or pull() operation calls. The push() operation takes a single parameter with data for the event. Event data for pull() is included in the return value so the operation has no parameters. In both cases, the event data is of type any which allows any IDL defined data type to be passed. In order to use untyped event data, both the supplier and consumer must agree as to the contents of any.
In typed communication, application-specific IDL interfaces are defined by the programmer. Rather than using push() and pull() operations and transmitting data with parameters of type any, the programmer defines an interface suppliers and consumers can use for communicating events. Parameters may be of any type defined in the IDL. To initiate communication using the Push method, operations defined in the interface are invoked. In the Pull method, event communication is initiated by invoking operations that act on the interface.
Summary Contents
- Communicating Indirectly
- Event Transfer And Communication
- Event Example
- Programming Interface
- Untyped Push < Next
- Untyped Pull
- Typed Push
- Typed Pull
