MetaData » History » Version 1
J. Wienke, 05/27/2011 05:37 PM
| 1 | 1 | J. Wienke | h1. Meta Data |
|---|---|---|---|
| 2 | 1 | J. Wienke | |
| 3 | 1 | J. Wienke | Events carry a set of meta data with themselves. These are: |
| 4 | 1 | J. Wienke | |
| 5 | 1 | J. Wienke | * *senderId*: ID of the sending |
| 6 | 1 | J. Wienke | * *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. |
| 7 | 1 | J. Wienke | * *sendTime*: the time at which the generated notification for an event was sent on the bus (after serialization) |
| 8 | 1 | J. Wienke | * *rawReceiveTime*: the time at which an event is received by listener in its encoded form |
| 9 | 1 | J. Wienke | * *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) |
| 10 | 1 | J. Wienke | * *userTimes*: a set of key-value user-defined time-stamps |
| 11 | 1 | J. Wienke | |
| 12 | 1 | J. Wienke | 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. |