You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Justin Ross (JIRA)" <ji...@apache.org> on 2016/11/04 14:55:58 UTC

[jira] [Updated] (PROTON-985) Modify pn_transport_tick to explicitly use a monotonic clock, not wall clock time

     [ https://issues.apache.org/jira/browse/PROTON-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Justin Ross updated PROTON-985:
-------------------------------
    Fix Version/s: 0.17.0

> Modify pn_transport_tick to explicitly use a monotonic clock, not wall clock time
> ---------------------------------------------------------------------------------
>
>                 Key: PROTON-985
>                 URL: https://issues.apache.org/jira/browse/PROTON-985
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.10
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>             Fix For: 0.17.0
>
>
> The timestamp argument to pn_transport_tick is a pn_timestamp_t.  pn_timestamp_t implies real time (wall clock) in that it's expressed as a time value based on epoch.
> As seen in QPID-6698, using a real time value for that argument can lead to problems if the real time is adjusted (eg.  timezone, daylight savings, drift).
> Instead, pn_transport_tick should be passed a monotonic clock source - one that does not reflect changes in real time.
> All documentation and examples should be updated accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org