![[ChimeraX Issue Tracking System]](/trac/ChimeraX/chrome/site/ChimeraX-icon.svg){kind=icon}
Opened 5 years ago
Last modified 5 years ago
#3321 assigned enhancement
remotecontrol subcommands on/off keywords inconsistent
| Reported by: | Elaine Meng | Owned by: | Tom Goddard |
|---|---|---|---|
| Priority: | moderate | Milestone: | |
| Component: | Input/Output | Version: | |
| Keywords: | Cc: | ||
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
Currently the REST subcommand takes start/stop and the XMLRPC one takes on/off (= true/false).
I don't feel strongly as to which is better, would just like these two subcommands of "remotecontrol" to have the same choices of words for turning them on and off. The difference makes it hard to remember which words to use for which method.
Maybe changing the REST one is slightly better since "device" subcommands also use on/off (=true/false).
Note:
See TracTickets
for help on using tickets.
"remotecontrol rest start" and "remotecontrol rest stop" and "remotecontrol rest port" are subcommands that all take different options, while "remotecontrol xmlrpc" is a subcommand and on/off is a boolean option. Conrad wrote the rest commands (it is in the rest_server bundle) and I wrote the xmlrpc commands. I am not enthusiastic about changing either of them. The rest commands may actually be used by some users as there has been mailing list discussion. The xmlrpc one is so obscure it could possibly be dropped -- it was a test when we were applying for the P41 grant and wanted to mention ChimeraX talking to Phenix. Phenix used XMLRPC at that time. We have also had meetings about significantly improving and changing the rest method. So both methods are experimental and probably someday both will be replaced.