Having followed this thread from the beginning, I have to agree with Nicolas on this. What you are proposing are Account Manager features.
The user chooses to use an account manager so they do not HAVE to run around to each machine to make changes. If you want to extend the features of the account manager to provide non-Boinc related tasks that is fine. The user can attach to the account manager you design and use whatever features you choose to provide. Thanks, Jim -------- Jim Preston BOINC Support Volunteer [email protected] SKYPE jhparizona-boinc On Feb 23, 2010, at 11:00 AM, Nicolás Alvarez wrote: > On 2/23/10, Mark Pottorff <[email protected]> wrote: >> Allowing one project to abort another project's tasks should only >> be allowed >> with the user's consent. > > Allowing one project to do anything with the core client, be it abort > other project's tasks, or even detach *itself*, should never be > allowed at all. > _______________________________________________ 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.
