Uploaded image for project: 'REEF (Retired)'
  1. REEF (Retired)
  2. REEF-1532

Pass Time object instead of numeric timestamp in Timer methods

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: In Progress
    • Major
    • Resolution: Unresolved
    • None
    • None
    • REEF-Common

    Description

      Methods in Timer interface, e.g. Timer.isReady() accept long timestamp, but in all contexts where the Timer implementations are used, we operate with Time objects. That leads to awkward chain calls, e.g.

      timer.getDuration(event.getTimeStamp())

      instead of shorter and more readable and type safe

      timer.getDuration(event)

      We propose to deprecate methods that take long timestamp in release 0.16 in favor of parameters of type Time and remove old methods in teh subsequent release.

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. REEF-1868 Release 0.17

          • Major - Major loss of function.
          • Open
          is blocked by

          Task - A task that needs to be done. REEF-1444 Release 0.16

          • Major - Major loss of function.
          • Resolved
          requires

          Sub-task - The sub-task of the issue REEF-1527 Graceful shutdown of the RuntimeClock is not so graceful: unconditionally clears the event queue

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              motus Sergiy Matusevych
              motus Sergiy Matusevych
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: