A list of references to events (via their event ids) which caused a given event.
See Event for more.
Mechanism that transforms event payloads into data of a particular wire type and vice-versa.
The type (programming language dependent) of event payload.
Example(C++,protocol buffers,spread): IplImage* for the example above
Mechanism that transforms event payloads into data of the wire type that has an interpretation w.r.t. the wire schema. Uniquely identified by the triple
Example(C++,protocol buffers,spread): AbstractConverter<std::string>?
See Types for a list of well-known wire schema <-> data type mappings.
For events in RSB, see Event.
See [Luckham2001PEI] for a general treatment.
Unique identifier of an Event.
See Event for more.
A kind of transport, which delivers events within one process (i.e. no inter-process or network communication).
See Inprocess Transport.
A kind of participant which asynchronously receives events.
See also reader.
A kind of participant which provides methods that can be called by other participants.
See also remote server.
In the context of RSB, meta-data refers pieces of data attached to events in addition to the payload.
A data field in RSB events which specifies the role of a given event within a communication pattern. For example, the request/reply communication pattern uses the values "REQUEST" and "REPLY".
See Method for more.
transport -specific message that contains
Domain object (programming language dependent) that is associated with an event.
Example(C++,protocol buffers,spread): an object of type IplImage*
A particular extension of RSB‘s functionality, such as a transport implementation or a converter, packaged as runtime-loadable code.
See Plugins.
A kind of participant which synchronously receives events.
See also listener.
A kind of participant which is able to call methods provided by local servers.
See also local server.
Descriptor for a channel of the unified bus. The channel is itself hierarchical, hence the scope also reflects this structure.
See Scope.
A positive integer associated to each event which indicates the order of all events published by a particular informer.
See Sequence Number.
A given scope has a potentially infinite number subscopes. All events visible in a subscope of a scope are visible in the scope itself.
For example, /a/b is a subscope of the scope /a.
See superscope, Scope.
A given scope has zero or more proper superscopes. Each superscope has the property that all events visible in the original scope are also visible in the superscope.
For example, / is a superscope of all scopes and proper superscope of all scopes except / itself. /a/b is a proper superscope of /a/b/c, /a/b/d, /a/b/c/d, etc but not /a or /a/c.
Mechanism for transporting notifications from their origin to their destinations. Most transports correspond to a network protocol.
See Transports.
Layout/structure of serialized representation of event payload.
Example(C++,protocol buffers,spread): specified by ImageMessage protocol buffer descriptor
Container type (programming language dependent?) of serialized representation of event payload (specific for a port type).
Examples