Changes between Version 2 and Version 3 of ClientLogic

Timestamp:

May 3, 2007, 1:08:34 PM (17 years ago)

Author:

Simek

Comment:

little visual change

ClientLogic

@@ -27 +27 @@
 The various functions called are as follows:
 
-'''check_suspend_activities''' checks for conditions such as recent mouse/keyboard input, or running on batteries, in which user preferences dictate that no work be done.
+ * '''check_suspend_activities''' checks for conditions such as recent mouse/keyboard input, or running on batteries, in which user preferences dictate that no work be done.
 
-'''net_xfers->poll(), http_ops->poll(), file_xfers->poll()
-and pers_xfers->poll()''' manage the internal transitions of the various FSM layers.
+ * '''net_xfers->poll(), http_ops->poll(), file_xfers->poll() and pers_xfers->poll()''' manage the internal transitions of the various FSM layers.
 
-'''start_apps()''' checks whether it's possible to start an application, i.e. a CPU slot is vacant and there's a result with all its input files present. If so it starts the application.
+ * '''start_apps()''' checks whether it's possible to start an application, i.e. a CPU slot is vacant and there's a result with all its input files present. If so it starts the application.
 
-'''handle_running_apps()''' checks whether a running application has exited, and if so cleans up after it.
+ * '''handle_running_apps()''' checks whether a running application has exited, and if so cleans up after it.
 
-'''handle_pers_file_xfers()''' starts new file transfers as needed.
+ * '''handle_pers_file_xfers()''' starts new file transfers as needed.
 
-'''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.
+ * '''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.
 
-'''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.
+ * '''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.