On Wed, May 26, 2010 at 12:29 PM, Josef W. Segur <[email protected]> wrote: > As has been mentioned a few times, there's a fundamental difficulty > in applying host punishment quickly because it can depend on when > a result is validated.
Not if there are strict(er) rules to what is "a valid result". Is a valid result just those that are not returned immediately with an error, or is it all work after validation? Is it strictly about the work being done, or is it to safe-guard against "wrong-doings with credit"? At this moment a valid result is work returned before the deadline and without errors, but prior to validation. E.g. at this moment - taking Seti again as an example - there are Linux computers out there that return valid results that show zero CPU time, thus claim zero credit. If paired against another box claiming zero credits... There are also all_platform computers out there that still run BOINC 4.xx, which categorically claim zero credit. And usually everyone in that group gets those zero credits, as the work is validated as being correct. If it's strictly about work being returned immediately with an error, then the present restrictions may be adequate. If it's to safe-guard against zero CPU time claimers who apparently (after validation) return good work, does there need to be something else done? What? If it's to safe-guard against zero credit claimers/zero credit granters? The best solution is to get them to update to a newer version, but how? -- -- Jord. _______________________________________________ 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.
