Changes between Version 2 and Version 3 of ClientLogic
- Timestamp:
- 05/03/07 13:08:34 (3 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ClientLogic
v2 v3 27 27 The various functions called are as follows: 28 28 29 '''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.29 * '''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. 30 30 31 '''net_xfers->poll(), http_ops->poll(), file_xfers->poll() 32 and pers_xfers->poll()''' manage the internal transitions of the various FSM layers. 31 * '''net_xfers->poll(), http_ops->poll(), file_xfers->poll() and pers_xfers->poll()''' manage the internal transitions of the various FSM layers. 33 32 34 '''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.33 * '''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. 35 34 36 '''handle_running_apps()''' checks whether a running application has exited, and if so cleans up after it.35 * '''handle_running_apps()''' checks whether a running application has exited, and if so cleans up after it. 37 36 38 '''handle_pers_file_xfers()''' starts new file transfers as needed.37 * '''handle_pers_file_xfers()''' starts new file transfers as needed. 39 38 40 '''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.39 * '''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. 41 40 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.41 * '''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.
