Hi, This is to share my observations and practices mainly with people using `remotecontrol xmlrpc`, likely developers. `xmlrpc` has a very high overhead, `remotecontrol rest` with "multipart/form-data" header POST requests should be a better option. First, the REST method can also be used programmatically in scripts or applications fairly easily. I have been sending GET requests using the REST method. Then, I hit "Request-URI Too Long" as I am sending decent sized json data (17KB). Then I tried XML-RPC and realized the frame rate dropped from 58 to 8. The frame rate can be displayed at the status line via `graphics rate true`. Then GPT guided me to try POST with "application/x-www-form-urlencoded" as Content-Type. I got stuck here for a while and found _parse_post <https://github.com/RBVI/ChimeraX/blob/3233aaaf01623ca24bccff7196410401872ce5...> returns "fields" in binary and the program could not parse args["command"] <https://github.com/RBVI/ChimeraX/blob/3233aaaf01623ca24bccff7196410401872ce5...> as what's inside is b"command". Then I refactored my client to POST with "multipart/form-data" and it worked. More details in my conversations with bots: URL too long: https://chatgpt.com/share/682c856c-174c-8003-bfc9-96fa7e2db0c3 Frame rate cmd: https://chatgpt.com/share/682c8589-2da0-8003-8c14-a59b75927c6b XML-RPC overhead: https://chatgpt.com/share/682c85a7-5f40-8003-8615-095e0a28fccd POST: https://chatgpt.com/share/682c85ca-9938-8003-bb0b-1fb7dd7938ef Best, Roden -- This message and its contents, including attachments are intended solely for the original recipient. If you are not the intended recipient or have received this message in error, please notify me immediately and delete this message from your computer system. Any unauthorized use or distribution is prohibited. Please consider the environment before printing this email.