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.

diff --git a/extras/rpc-spec.txt b/extras/rpc-spec.txt
index 35ba35d81e78477b9bd81cdfe8587af270c16e0f..488115404a26f1b39e3e37d23b75e253f1402219 100644 (file)
--- a/extras/rpc-spec.txt
+++ b/extras/rpc-spec.txt
@@ -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