Abstract parent interface for VirtualBox events. More...
|Internal method called by the system when all listeners of a particular event have called IEventSource::eventProcessed. |
|void||waitProcessed (in long timeout,[retval] out boolean result)|
|Wait until time outs, or this event is processed. |
|readonly attribute VBoxEventType||type|
|Event type. |
|readonly attribute IEventSource||source|
|Source of this event. |
|readonly attribute boolean||waitable|
|If we can wait for this event being processed. |
Abstract parent interface for VirtualBox events.
Actual events will typically implement a more specific interface which derives from this (see below).
Introduction to VirtualBox events
Generally speaking, an event (represented by this interface) signals that something happened, while an event listener (see IEventListener) represents an entity that is interested in certain events. In order for this to work with unidirectional protocols (i.e. web services), the concepts of passive and active listener are used.
Event consumers can register themselves as listeners, providing an array of events they are interested in (see IEventSource::registerListener). When an event triggers, the listener is notified about the event. The exact mechanism of the notification depends on whether the listener was registered as an active or passive listener:
Waitable events are useful in situations where the event generator wants to track delivery or a party wants to wait until all listeners have completed the event. A typical example would be a vetoable event (see IVetoEvent) where a listeners might veto a certain action, and thus the event producer has to make sure that all listeners have processed the event and not vetoed before taking the action.
A given event may have both passive and active listeners at the same time.
Any VirtualBox object capable of producing externally visible events provides an
eventSource read-only attribute, which is of the type IEventSource. This event source object is notified by VirtualBox once something has happened, so consumers may register event listeners with this event source. To register a listener, an object implementing the IEventListener interface must be provided. For active listeners, such an object is typically created by the consumer, while for passive listeners IEventSource::createListener should be used. Please note that a listener created with IEventSource::createListener must not be used as an active listener.
Once created, the listener must be registered to listen for the desired events (see IEventSource::registerListener), providing an array of VBoxEventType enums. Those elements can either be the individual event IDs or wildcards matching multiple event IDs.
After registration, the callback's IEventListener::handleEvent method is called automatically when the event is triggered, while passive listeners have to call IEventSource::getEvent and IEventSource::eventProcessed in an event processing loop.
The IEvent interface is an abstract parent interface for all such VirtualBox events coming in. As a result, the standard use pattern inside IEventListener::handleEvent or the event processing loop is to check the type attribute of the event and then cast to the appropriate specific interface using
Internal method called by the system when all listeners of a particular event have called IEventSource::eventProcessed.
This should not be called by client code.
|void IEvent::waitProcessed||(||in long||timeout,|
|[retval] out boolean||result|
Wait until time outs, or this event is processed.
Event must be waitable for this operation to have described semantics, for non-waitable returns true immediately.
|timeout||Maximum time to wait for event processing, in ms; 0 = no wait, -1 = indefinite wait.|
|result||If this event was processed before timeout.|
|readonly attribute boolean IEvent::waitable|
If we can wait for this event being processed.
If false, waitProcessed returns immediately, and setProcessed doesn't make sense. Non-waitable events are generally better performing, as no additional overhead associated with waitability imposed. Waitable events are needed when one need to be able to wait for particular event processed, for example for vetoable changes, or if event refers to some resource which need to be kept immutable until all consumers confirmed events.