What I was planning at the client (which seems to be nixed) was to collect
the information at several levels, and use the finest grained one with
sufficient information to be useful (2 tasks minimum).
jm7
Eric Myers
<[email protected]
et> To
Sent by: David Anderson
<boinc_dev-bounce <[email protected]>
[email protected] cc
u> [email protected]
Subject
Re: [boinc_dev] Preemption of very
03/25/2010 11:28 short tasks.
AM
On Fri, 19 Mar 2010, David Anderson wrote:
>
> Good point. I'll add that, though it should be per app, not app version.
> Here's a summary of new database items:
>
> (1) = brand new
> (2) = moved from the project config file
> (3) = moved from the host table
> ....
> Any other suggestions?
Not to be overly complex, but does it make sense to _add_ these
at finer scope rather than moving them, and then let the finest
scope, if specified, take precidence?
So if specified at rhe per-project level, use that,
but per-app would override,
or per-app-version would override that, but only if specified.
Mabye harder to code, but perhaps easier to transition to,
easier to use, and more flexible?
-Eric
_______________________________________________
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.
_______________________________________________
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.
