Qpid Proton
  1. Qpid Proton
  2. PROTON-475

[python] Proton wrapper API's use of time values is inconsistent

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.5
    • Fix Version/s: 0.6
    • Component/s: proton-c
    • Labels:
      None

      Description

      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.

        Activity

        Hide
        ASF subversion and git services added a comment -

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

        PROTON-475: use seconds-based timeout values

        Show
        ASF subversion and git services added a comment - Commit 1549639 from Ken Giusti in branch 'proton/trunk' [ https://svn.apache.org/r1549639 ] PROTON-475 : use seconds-based timeout values

          People

          • Assignee:
            Ken Giusti
            Reporter:
            Ken Giusti
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development