Oberon ||
Library ||
Module Index ||
Search Engine ||
Definition ||
Module
Ulm's Oberon Library:
RemoteEvents
NAME
RemoteEvents - support export and import of event types
DESCRIPTION
RemoteEvents
offers the RemoteObjects service (see Services)
for event types of Events.
Note that RemoteEvents supports a subset of
the operations of Events for event types only:
- The priority of event types is initially shared but not maintained,
i.e. priority changes do not affect other proxy objects
or the original object.
- Changes of the reaction type are not propagated to other proxy objects
or the original object.
Moreover, setting the reaction type to Events.ignore or
Events.default at the side of the original object causes
the support of RemoteEvents to be partially lost.
This effect can be undone only by using Events.SaveReaction
and Events.RestoreReaction.
- Events.Manager works locally only.
If an event gets raised on any of the sides it is forwarded
(by using PersistentEvents) to all other sides.
Events types are therefore (with the support of RemoteEvents)
a good technique for broadcasting events among all interested
parties even if they reside in other address spaces.
Because RemoteEvents takes advantage of Shadows
broadcasts are distributed in a parallelized way.
DIAGNOSTICS
RemoteEvents
does not generate any error events on its own but causes
the error events of RemoteObjects to be related
to the event type (see RelatedEvents).
SEE ALSO
- Events
-
general event handling
- PersistentEvents
-
supports the persistence of events
- RemoteObjects
-
delegation of operations to remote objects
BUGS
BlockingEvents are not supported yet but look as if they
would be due to the hierachical definition of service providers
(see Services).
Edited by: borchert, last change: 1995/12/19, revision: 1.1, converted to HTML: 1997/04/28
Oberon ||
Library ||
Module Index ||
Search Engine ||
Definition ||
Module