Following on from my previous thought, it seems that we aren't paying enough attention to the scope of some of these settings.
An XML entity has two different scopes: a scope for the DEFINITION a scope for the VALUE Many BOINC preferences are global for both definition and value. They tend to be stored in prefs.xml (global or override). Other preferences are project-specific for both definition and value, like the screen-saver controls Nicolas reminded us of . They live in account.xml and client_state.xml. But there's a third class, with a global definition scope but a project value scope, which seems to me to be under-utilised. In fact, it has only one member: resource share. I propose that we examine the recent resource additions, and consider whether more of them should be moved into the middle scope (global def, project value). Use/don't use CPU/GPU is an obvious place to start, but others might be considered: suspend (CPU/GPU) while in use might be another candidate - different project apps interfere with the desktop to different degrees, and I might be willing to let GPUGrid, for example, run a CUDA app while I'm active, but not willing to run an AQUA CUDA app. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
