Changeset 11735


Ignore:
Timestamp:
Jan 21, 2011, 2:29:26 AM (11 years ago)
Author:
jordan
Message:

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.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/extras/rpc-spec.txt

    r11686 r11735  
    4545   since the port and path may be changed to allow mapping and/or multiple
    4646   daemons to run on a single server.
    47 
    48    In addition to POSTing, there's also a simple notation for sending
    49    requests in the query portion of a URL.  This is not as robust, but can
    50    be useful for debugging and simple tasks.  The notation works as follows:
    51 
    52    (1) Any key not "tag" or "method" is treated as an argument.
    53    (2) The "arguments" key isn't needed, since data isn't nested.
    54    (3) If the value in a key/value pair can be parsed as a number, then it is.
    55        Otherwise if it can be parsed as an array of numbers, then it is.
    56        Otherwise, it's parsed as a string.
    57 
    58    Examples:
    59    ?method=torrent-start&ids=1,2
    60    ?method=session-set&speed-limit-down=50&speed-limit-down-enabled=1
    61    
    6247
    63483.  Torrent Requests
Note: See TracChangeset for help on using the changeset viewer.