Bug #2472
Under windows rsc::misc timestamps are in milliseconds.
Status: | In Progress | Start date: | 12/10/2015 | ||
---|---|---|---|---|---|
Priority: | Normal | Due date: | |||
Assignee: | J. Moringen | % Done: | 80% | ||
Category: | Operating System Abstraction | ||||
Target version: | - |
Description
under windows the send timestamp of the spread transport seems to be in milliseconds.
As Jan already found out the problem resides in the rsc::misc function for gathering the current timestamp (sorry, forgot the name...).
Here is a printout of a rsb-loggercpp that shows the data received from the windows host on a linux machine. Note the send timestamp.
------------------------------------------------------------------------------- Event Scope /kinect2_old/persontracking/state/5/ Id EventId[participantId = UUID[2c098dad-ab20-4e39-8c70-39330fb7a5c4], sequenceNumber = 2] Type bytearray Origin 2c098dad-ab20-4e39-8c70-39330fb7a5c4 Timestamps Create 2015-Dec-10 15:16:13.341861+??:?? Send 2015-Dec-10 15:16:13.341000+??:?? Receive 2015-Dec-10 15:16:13.342695+??:?? Deliver 2015-Dec-10 15:16:13.342696+??:?? Payload (bytearray, length 4) 0x0000 0a 02 08 05 -------------------------------------------------------------------------------
History
#1 Updated by J. Moringen about 6 years ago
- Status changed from New to In Progress
- Assignee set to J. Moringen
- % Done changed from 0 to 80
#2 Updated by J. Moringen about 6 years ago
- Subject changed from under windows rsc::misc timestamps are in milliseconds. to Under windows rsc::misc timestamps are in milliseconds.
- Category set to Operating System Abstraction