-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Saving timestamp in message header #5
Comments
Hi Yusen, I just pushed out a new release for the plugin (0.3.2) that adds the current unix timestamp in milliseconds to all message headers. If you're sending messages between machines, you'll need an independent way of determining the offset between the two system clocks. |
Thanks! I will test it soon. |
Cool! Fyi, the |
Just a small request, for latency measurement purposes in real time applications, can we have a timestamp in the header? Like, take a unix timestamp at creating c_obj for header and put it into a timestamp field in the header.
Also, would it be possible to take another timestamp after the message is sent to see how long it takes on the sending side to send the message and log it somewhere? I am assuming the sending on zeromq is efficient but it would be better to check it as well. Maybe we can store this timestamp and send it in the next message?
The text was updated successfully, but these errors were encountered: