Bug #390
Handling of sendTime in Informer
| Status: | New | Start date: | 06/23/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Specification | |||
| Target version: | rsb-1.0 |
Description
An Informer returns an Event to the caller after sending it. This is especially useful if the event is created in the informer on behalf of the calling client. Currently, returned events have their sendTime timestamp set in some way. However, it is not quite clear, how this timestamp should be set. There are (at least) the following possibilities:
- The informer sets the timestamp before passing the event to connectors for sending
- Each connector somehow locks the event and sets the timestamp. The least recent connector "wins"
- The connector sets the timestamp only if there is just one connector
- The informer sets the timestamp after the event has been processed by all connectors
After this has been decided, update
- UML sequence diagrams
- EventProcessing
- Implementations
History
#1 Updated by J. Moringen almost 13 years ago
- Description updated (diff)
#2 Updated by J. Moringen almost 13 years ago
- Category set to Specification
- Target version set to rsb-0.10
#3 Updated by J. Moringen over 10 years ago
- Target version changed from rsb-0.10 to rsb-0.11
#4 Updated by S. Wrede over 9 years ago
- Target version changed from rsb-0.11 to rsb-1.0