Posts by sgaboinc

1) Message boards : API : feature request gui-rpc boinc client events and xml (Message 66247)
Posted 18 Dec 2015 by sgaboinc
Post:
i tried using boinccmd for some automation tasks
however, boinccmd output isn't quite 'machine readable', i.e. it is hard to use another utility to do automation tasks such as a custom if-this-then-do-that custom scheduling and automation. i'd suggest having an xml output option so that utility apps can be written to do custom automation/scheduling etc. i'd suggest having an xml output option so that utility apps can be written to do custom automation/scheduling etc
(xml is much more structured to be parsed by another app for interfacing etc)

the other feature i'd like to see is could gui-rpc be enhanced to send *events* messages?
e.g. and event can be sent when a task started downloading, finished downloading, started running, completed, etc

the purpose of which is to enable *automation* which could be for various boinc tasks, or it could extend well beyond simply boinc, e.g. when a certain number of tasks complete, to suspend/shutdown the system etc
2) Message boards : BOINC client : feature request gui-rpc boinc client events and xml (Message 66246)
Posted 18 Dec 2015 by sgaboinc
Post:
i tried using boinccmd for some automation tasks
however, boinccmd output isn't quite 'machine readable', i.e. it is hard to use another utility to do automation tasks such as a custom if-this-then-do-that custom scheduling and automation. i'd suggest having an xml output option so that utility apps can be written to do custom automation/scheduling etc
(xml is much more structured to be parsed by another app for interfacing etc)

the other feature i'd like to see is could gui-rpc be enhanced to send *events* messages?
e.g. and event can be sent when a task started downloading, finished downloading, started running, completed, etc

the purpose of which is to enable *automation* which could be for various boinc tasks, or it could extend well beyond simply boinc, e.g. when a certain number of tasks complete, to suspend/shutdown the system etc



Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.