qpid-proton git commit: NO-JIRA: c proactor API doc clarify use of pn_proactor_now()

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

qpid-proton git commit: NO-JIRA: c proactor API doc clarify use of pn_proactor_now()

aconway-2
Repository: qpid-proton
Updated Branches:
  refs/heads/master c31e2ecf0 -> cd5551778


NO-JIRA: c proactor API doc clarify use of pn_proactor_now()


Project: http://git-wip-us.apache.org/repos/asf/qpid-proton/repo
Commit: http://git-wip-us.apache.org/repos/asf/qpid-proton/commit/cd555177
Tree: http://git-wip-us.apache.org/repos/asf/qpid-proton/tree/cd555177
Diff: http://git-wip-us.apache.org/repos/asf/qpid-proton/diff/cd555177

Branch: refs/heads/master
Commit: cd555177884db35fb2b361844041ee2e498d7c17
Parents: c31e2ec
Author: Alan Conway <[hidden email]>
Authored: Fri Jun 9 15:52:45 2017 -0400
Committer: Alan Conway <[hidden email]>
Committed: Fri Jun 9 15:52:45 2017 -0400

----------------------------------------------------------------------
 proton-c/include/proton/proactor.h | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/qpid-proton/blob/cd555177/proton-c/include/proton/proactor.h
----------------------------------------------------------------------
diff --git a/proton-c/include/proton/proactor.h b/proton-c/include/proton/proactor.h
index 9c7ce59..4e5151a 100644
--- a/proton-c/include/proton/proactor.h
+++ b/proton-c/include/proton/proactor.h
@@ -279,8 +279,12 @@ PNP_EXTERN pn_proactor_t *pn_event_proactor(pn_event_t *event);
 /**
  * Get the real elapsed time since an arbitrary point in the past in milliseconds.
  *
- * This may be used as a portable way to get a timestamp for the current time. It is monotonically
- * increasing and will never go backwards.
+ * This may be used as a portable way to get a process-local timestamp for the
+ * current time. It is monotonically increasing and will never go backwards.
+ *
+ * Note: this is not a suitable value for an AMQP timestamp to be sent as part
+ * of a message.  Such a timestamp should use the real time in milliseconds
+ * since the epoch.
  *
  * @note Thread safe.
  */


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Loading...