mirror of
https://github.com/transmission/transmission
synced 2025-03-03 18:25:35 +00:00
Remove the documentation for PUT notation from the rpc spec
The PUT hack was useful back when Transmission's RPC was first written, but it doesn't scale well to any of the commands that make its RPC useful. We should deprecate its use and not advertise this feature anymore.
This commit is contained in:
parent
260c4470cf
commit
ab02ba0d2c
1 changed files with 0 additions and 15 deletions
|
@ -45,21 +45,6 @@
|
|||
since the port and path may be changed to allow mapping and/or multiple
|
||||
daemons to run on a single server.
|
||||
|
||||
In addition to POSTing, there's also a simple notation for sending
|
||||
requests in the query portion of a URL. This is not as robust, but can
|
||||
be useful for debugging and simple tasks. The notation works as follows:
|
||||
|
||||
(1) Any key not "tag" or "method" is treated as an argument.
|
||||
(2) The "arguments" key isn't needed, since data isn't nested.
|
||||
(3) If the value in a key/value pair can be parsed as a number, then it is.
|
||||
Otherwise if it can be parsed as an array of numbers, then it is.
|
||||
Otherwise, it's parsed as a string.
|
||||
|
||||
Examples:
|
||||
?method=torrent-start&ids=1,2
|
||||
?method=session-set&speed-limit-down=50&speed-limit-down-enabled=1
|
||||
|
||||
|
||||
3. Torrent Requests
|
||||
|
||||
3.1. Torrent Action Requests
|
||||
|
|
Loading…
Reference in a new issue