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

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)

sgaboinc hi - the wiki is a great source, i suggest this client_state.xml may be close.

This is an important page to read here

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

If by "event", you mean "log an entry to a log file", then this also exists at many levels. Each task as it completes, for example adds a record to job_<project>.txt other actions are logged elsewhere.

Again the wiki is a good place to start, and there are *many* configuration options to control boinc.

hth

This is a good idea.
I suggest JSON rather than XML because it's more human-readable.
The changes would be entirely in lib/gui_rpc_client_print.cpp.
I don't have time to do this, but maybe someone else does.
I suggest creating an issue on Github.

Currently the GUI RPC mechanism is one-directional: requests are GUI->client.
Adding client->GUI requests would be a large change.
You can do most of what you want with periodic polling.

-- David

---