Enhancement #1961
Preserve original send times
Status: | Resolved | Start date: | 08/25/2014 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | J. Wienke | % Done: | 100% | |
Category: | Python Client API | |||
Target version: | - |
Description
Since sending events through RSB always creates new send times, there should be a way to preserve the original send times in the events. I would propose the attached patch which transfers the send time into a user meta data item.
Associated revisions
Pass through the original send time
Put the original event send time to userTimes['original_send'] so that
clients can access this value if required.
fixes #1961
History
#1 Updated by J. Wienke over 9 years ago
Any objections against this patch? Cause I stumbled upon this again.
#2 Updated by J. Moringen over 9 years ago
- Assignee changed from J. Moringen to J. Wienke
Any objections against this patch? Cause I stumbled upon this again.
The whole protocol is suboptimal at the moment, but the situation with the patch is probably better than without it. So yes, go ahead.
#3 Updated by J. Wienke over 9 years ago
- Status changed from New to In Progress
#4 Updated by J. Wienke over 9 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset rsbag-python|b33f4ac5529f022e4e4ebe7e6f45ec299c672994.