Events¶

Conceptually and when represented in programs, RSB Events consist of the following components:

• An ID (which is a UUID)
• A destination scope
• A data-type
• A method?
• A payload
• Meta Data (see below)

Meta Data¶

Events carry a set of meta data with themselves. Some meta data items are specified and processed by RSB while other others are user-defined and not interpreted by RSB.

RSB Meta Data Items¶

The current set of specified, required meta data items is given below:

• senderId: ID (a UUID) of the sending participant.
• eventCreationTime: a time stamp that is automatically filled with the time the event instance was created by the language binding. This should usually reflect the time at which the notified condition most likely occurred in the sender. If event instances are reused, it has to be reset manually by the client.
• sendTime: the time at which the generated notification for an event was sent on the bus (after serialization)
• rawReceiveTime: the time at which an event is received by listener in its encoded form
• receiveTime: the time at which an event was decoded and will be dispatched to the client as soon as possible (set directly before passing it to the client handler)

User-defined Meta Data Items¶

• userTimes: a set of key-value user-defined time-stamps

All timestamps are represented using microseconds precision (even if the OS cannot provide real microseconds). eventCreationTime and sendTime and userTimes are computed by the local clock of the sending process, whereas rawReceiveTime and receiveTime are filled by the receiving participant's local clock.