qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PROTON-475) [python] Proton wrapper API's use of time values is inconsistent
Date Mon, 09 Dec 2013 18:36:07 GMT

    [ https://issues.apache.org/jira/browse/PROTON-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843380#comment-13843380

ASF subversion and git services commented on PROTON-475:

Commit 1549639 from [~kgiusti] in branch 'proton/trunk'
[ https://svn.apache.org/r1549639 ]

PROTON-475: use seconds-based timeout values

> [python] Proton wrapper API's use of time values is inconsistent
> ----------------------------------------------------------------
>                 Key: PROTON-475
>                 URL: https://issues.apache.org/jira/browse/PROTON-475
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.5
>            Reporter: Ken Giusti
>            Assignee: Ken Giusti
>             Fix For: 0.6
> The precision used for timeout values in the Python API is inconsistent.  In some case
(messenger's timeout for example), timeouts are expressed in seconds using a float.   In other
cases, (driver wait(), etc), timeouts are expressed in milliseconds.
> To be consistent with the Python time module, we should be expressing timeout values
as seconds using a float.  
> There should be no change to the AMQP timestamp type, of course, which is defined as
milliseconds since unix epoch.

This message was sent by Atlassian JIRA

View raw message