Changeset 7867


Ignore:
Timestamp:
Feb 10, 2009, 6:19:09 PM (13 years ago)
Author:
charles
Message:

(trunk doc) tweak the RPC spec as suggested by chorlya

File:
1 edited

Legend:

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

    r7751 r7867  
    4949
    5050   HTTP POSTing a JSON-encoded request is the preferred way of communicating
    51    with a Transmission RPC server; however, a simple notation also exists
    52    for sending requests in the query portion of a URL.
    53 
    54    The URL notation works as follows:
     51   with a Transmission RPC server.  The current Transmission implementation
     52   has the default URL as http://host:9091/transmission/rpc.  Clients
     53   may use this as a default, but should allow the URL to be reconfigured,
     54   since the port and path may be changed to allow mapping and/or multiple
     55   daemons to run on a single server.
     56
     57   In addition to POSTing, there's also a simple notation for sending
     58   requests in the query portion of a URL.  This is not as robust, but can
     59   be useful for debugging and simple tasks.  The notation works as follows:
     60
    5561   (1) Any key not "tag" or "method" is treated as an argument.
    5662   (2) The "arguments" key isn't needed, since data isn't nested.
     
    6268   ?method=torrent-start&ids=1,2
    6369   ?method=session-set&speed-limit-down=50&speed-limit-down-enabled=1
     70   
    6471
    65723.  Torrent Requests
     
    245252      {
    246253         "arguments": {
    247              "fields": [ "id", "name", "totalSize" ]
     254             "fields": [ "id", "name", "totalSize" ],
     255             "ids": [ 7, 10 ]
    248256         },
    249257         "method": "torrent-get",
Note: See TracChangeset for help on using the changeset viewer.