org.mbs.services.cup.data

Class HEventSubscription

java.lang.Object

org.mbs.services.cup.data.SVEventSubscription

org.mbs.services.cup.data.HEventSubscription

public class HEventSubscription
extends SVEventSubscription

A structure contating propertiesneed for subscribing for hierarchy events.

Field Summary

Fields inherited from class org.mbs.services.cup.data.SVEventSubscription

eventTimeout, expiredEventsFilter, listenerRegProps

Constructor Summary

Constructors

Constructor and Description
HEventSubscription() Empty constructor.
HEventSubscription(java.util.Dictionary listenerRegProps, java.lang.String expiredEventsFilter, long eventTimeout) Creates a CUEventSubscription object with given attributes.

Method Summary

Methods inherited from class org.mbs.services.cup.data.SVEventSubscription

getExpiredEventsFilter, getListenerRegProps, getTimeout, read, write

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

HEventSubscription

public HEventSubscription()

Empty constructor.

HEventSubscription

public HEventSubscription(java.util.Dictionary listenerRegProps,
                          java.lang.String expiredEventsFilter,
                          long eventTimeout)

Creates a CUEventSubscription object with given attributes.

Parameters:

listenerRegProps - registration properties of the listener service. The HierarchyListener on the target framework to serve this subscription shall be registered with the registration properties applied with this argument.

expiredEventsFilter - - filter in ldap form, specifying the set of control units for which all hierachy events in which they participate as sub units should be delivered. An event is considered as expired if in the current event chunk of non-sent events, a hierarchy relation is subsequently attached and detached (or the opposite).In this case, both events are considered expired and by default will not be delivered. Expired event notifications are suitable for state machine applications that need the complete event sequence to realize their logic.

eventTimeout - max timeout (in milliseconds) after which every event should be delivered. Zero or negative number means that every event should be delivered without any delay. If it is a negative number – then the event notification shall be sent immediately within synchronous messages.
Specifying a delay is useful for increasing the performance of notifications sending – if two or more events are raised within a short time - they shall be delivered within a single packet.