Changes between Version 1 and Version 2 of ClientLogic


Ignore:
Timestamp:
Apr 24, 2007, 8:16:36 PM (17 years ago)
Author:
Nicolas
Comment:

Required manual changes to automatic script formatting. I think all those bold function and variable names should be monospaced instead.

Legend:

Unmodified
Added
Removed
Modified

  • ClientLogic

    v1 v2  
    22
    33The main loop of the core client repeatedly calls the following function:
    4 
    54
    65{{{
    … …  
    2322}
    2423}}}
    25   This function initiates new activities as needed, and checks for the completion of current activities. It is to be called periodically from either a sleep loop (command-line program) or timer handler of event loop (GUI program). It returns true if any change occurred, in which case it should be called again without sleeping.
     24
     25This function initiates new activities as needed, and checks for the completion of current activities. It is to be called periodically from either a sleep loop (command-line program) or timer handler of event loop (GUI program). It returns true if any change occurred, in which case it should be called again without sleeping.
    2626
    2727The various functions called are as follows:
    … …  
    4040'''garbage_collect()''' checks for objects that can be discarded. For example, if a file is non-sticky and is no longer referenced by any work units or results, both the FILE_INFO and the underlying file can be deleted. If a result has been completed and acknowledged, the RESULT object can be deleted.
    4141
    42 '''write_state_file_if_needed()''': any of the above functions that changes state in a way that should be written to client_state.xml (e.g. that needs to survive this execution of the core client) sets a flag '''client_state_dirty'''. write_state_file_if_needed() writes client_state.xml if this flag is set.
    43 
     42'''write_state_file_if_needed()''': any of the above functions that changes state in a way that should be written to client_state.xml (e.g. that needs to survive this execution of the core client) sets a flag '''client_state_dirty'''. '''write_state_file_if_needed()''' writes client_state.xml if this flag is set.