4.3. Web Page: Update Rates

About this task

Wait n seconds and then update the screen every n seconds represent command line arguments.

Enter values and CIMPLICITY will enter the complete argument in the HTML file.

Enter the following.

Field Command Line Argument/Description
Time without input 'til quiescent update rate. /WaitUpdate <seconds>
Webspace will continue to send updates to the client at the normal rate for the number of seconds entered until the user stops using the keyboard and/or mouse.
Time between updates when quiescent. /MinUpdate <seconds>
When the number of seconds to wait before the user stops using the keyboard and/or mouse have been reached, Webspace will begin the Time between updates when quiescent update rate and wait the number of seconds entered in the field between each update.
Time between updates during user input. /MaxUpdate <seconds>
Time between updates while the user is using the mouse and/or keyboard.
Important: Updates to clients require a trade-off between screen size/update frequency and server CPU usage; the more data a screen needs to transmit and more frequent the updates, the more CPU will be required. These factors in relation to the amount of RAM installed on the server, directly affect how many clients can connect at the same time.

A way to optimize update rates and the number of clients that can connect is to

Procedure

  1. Determine which screens need fast updates for some users and which can update more slowly.
  2. Create separate sessions to address the separate needs.
    1. Send screens that require faster updates to URL's that are different from screens requiring fewer updates.
    2. Enter different values for each screen update session; the values should address the update needs of that session only.

    A Relay server can be very useful to help balance the load.