4C Timeouts

4C Timeouts

4C supports timeouts on the server machine and on the client machine. Both server timeouts and client timeouts can be associated with either the current program or with the current session. A 4C server timeout can only be triggered when the 4C server program is idle and waiting for input. A 4C client timeout is only triggered when the client is idle regardless of whether the server is idle or not. The reasons that both client timeouts and server timeouts are necessary are:

There are several uses for timeouts including but not limited to:

The easiest way to define a server session timeout is by adding an entry to XLCONFIG similar to: For the above, if no <prname> is specified, the 4c server session will exit if it is waiting for input from the user for more than two hours. If <prname> is specified, then <prname> will run when the 4c server session has been waiting for user input for more than two hours.

The easiest way to define a client session timeout is by adding an entry to XLCONFIG similar to: For the above, if no <prname> is specified, the 4c client session will exit if there has been no mouse or keyboard input on the client machine for at least two hours. The 4csrvr may continue running if it is still doing useful work. If <prname> is specified, then <prname> will run when the 4c client session has been idle for at least two hours.

The only way to specify program timeouts is by calling sys.set_timeout() in the program that wants to timeout.

Examples Modify the config values by running demo.config.fm and then run run demo.main.s to see how the above examples work.

Notes:

See Also:

sys.settimeout()
sys.set_alarm()
sys.get_timeoutp()
sys.get_timeoutv()
sys.set_alarm()
sys.lock_clientws()
sys.exit_client()
sys.exit_4c()

Back to Top