ICEfaces
  1. ICEfaces
  2. ICE-4741

auctionMonitor configurable clock tick interval

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.8.1
    • Fix Version/s: 1.8.2-RC1, 1.8.2
    • Component/s: Sample Apps
    • Labels:
      None
    • Environment:
      ICEfaces
    • Affects:
      Sample App./Tutorial

      Description


      For load testing and demonstrations it is desirable to be able to configure the clock tick interval in the auctionMonitor demo at runtime.

        Activity

        Hide
        Ted Goddard added a comment -

        See if you would like to enhance it further. As a "security measure" I included a check that the interval must be greater than 500 milliseconds. This is appropriate for the public demo, but occasionally for performance testing it is useful to set the interval to 100 milliseconds (perhaps this should be the lower bound).

        Show
        Ted Goddard added a comment - See if you would like to enhance it further. As a "security measure" I included a check that the interval must be greater than 500 milliseconds. This is appropriate for the public demo, but occasionally for performance testing it is useful to set the interval to 100 milliseconds (perhaps this should be the lower bound).
        Hide
        Deryk Sinotte added a comment -

        The clock tick interval can now be changed via the administrative page that is included with the app (auctionControl.jspx). In addition, setTickInterval and getTickInterval are now available so that you can use a managed-property of the bean configuration to set the starting tick interval value. Resolving as fixed.

        Show
        Deryk Sinotte added a comment - The clock tick interval can now be changed via the administrative page that is included with the app (auctionControl.jspx). In addition, setTickInterval and getTickInterval are now available so that you can use a managed-property of the bean configuration to set the starting tick interval value. Resolving as fixed.
        Hide
        Deryk Sinotte added a comment -

        Changing it to a value below 1000 ms should still show the clock ticking every second. On the back-end, it will be attempting to do 10 pushes per second but since the time only really changes once per second, the other pushes should not result in any updates. Setting the interval about 1 second should slow the ticks depending on the interval. If the clocks stop ticking altogether when the interval is changed, then it's a bug.

        Show
        Deryk Sinotte added a comment - Changing it to a value below 1000 ms should still show the clock ticking every second. On the back-end, it will be attempting to do 10 pushes per second but since the time only really changes once per second, the other pushes should not result in any updates. Setting the interval about 1 second should slow the ticks depending on the interval. If the clocks stop ticking altogether when the interval is changed, then it's a bug.

          People

          • Assignee:
            Deryk Sinotte
            Reporter:
            Ted Goddard
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: