Orbacus Notify is the ideal foundation for your event-based applications. With new features like event filtering, structured events, and run-time system management, Orbacus Notify delivers all the flexibility you need to get your next project off the ground quickly and easily. Fully compliant with the CORBA Notification Service specification, Orbacus Notify provides a robust middleware platform for your distributed systems.View White Paper ›
- Provides flexibility via filtering for fast, easy project delivery
- Fully compliant with the CORBA Notification Service specification
- Fully backwards compatible with the OMG Event Service
- Supports push and pull delivery models, and hybrid combinations
- Supports all standard QoS and Admin properties
- Configure Notify to provide maximum performance
Event service compatibility
Orbacus Notify is fully backwards compatible with the OMG Event Service, providing a smooth migration path for your existing event service clients.
To maintain backwards compatibility with event service clients, Orbacus Notify supports untyped event delivery. In addition, Orbacus Notify introduces structured event and sequence structured event delivery.
Structured events enable you to specify per event QoS and compose events consisting of filterable and opaque fields. As structured events are actual IDL types, the filterable fields are visible to Orbacus Notify and are used during event filtering.
Sequence structured events
For small, individual events, the per-method command overhead may impact overall performance. If your clients frequently transfer small events, you may want to consider using sequence structured events.
In this scheme, one or more structured events are batched together and transferred in a single method invocation. Suppliers have full control of sequence composition and can accumulate a random number of events before actual delivery. Likewise, for consumers, Orbacus Notify enables you to configure the maximum batch size and pacing interval for event delivery.
Structured events are composed of an event header and event body, where the body consists of filterable and non-filterable fields. Through the use of mapping filters, Orbacus Notify supports the mapping of event header lifetime and priority property values. In effect, this mapping changes the way in which the event is handled within Orbacus Notify.
Forwarding filters enable you to filter event flow at various points throughout the service. This ensures that valuable network bandwidth on the consumer side is used purposefully and not by unwanted events.