This chapter describes the Notification Service Components and how they interact.
There are seven components in the OMG Notification Service architecture. These are described below:

'AND_OP'- or 'OR_OP'-type,
which determines if events must be validated using both the Administrators
associated Filter and/or its Proxy children Filters.
Pull or Push object. If the proxy is Push style
the client application must push events to the Proxy, otherwise the Proxy is
supposed to Pull events. The CosNotification::AdminProperties is
used to set the pacing interval.
Push proxy it will push events to the client
application.
When a Proxy is started it is set to accept CORBA::Any,
CosNotification::StructuredEvent or CosNotification::EventBatch
(a sequence of structured events).
If a Proxy is supposed to deliver structured events to a client application
and receives an CORBA::Any event, the event is converted to a
structured event with type_name set to "%ANY" and the
event is stored in remainder_of_body.
If a Proxy is supposed to deliver CORBA::Any events to a client application
and receives a structured event, the event is stored in an Any type. The
Any Type Code will be equal to the CosNotification::StructuredEvent
Type Code.