comparison doc/xmlrpc.txt @ 3969:905faf52a51f 1.4.3

fix mysql breakage in 1.4.2
author Richard Jones <richard@users.sourceforge.net>
date Wed, 27 Feb 2008 08:32:51 +0000
parents 53b922e0d2b7
children a70dbbc7f967
comparison
equal deleted inserted replaced
3968:5857cd1a0db9 3969:905faf52a51f
34 ---------- 34 ----------
35 The server currently implements four methods. Each method requires that the 35 The server currently implements four methods. Each method requires that the
36 user provide a username and password in the HTTP authorization header in order 36 user provide a username and password in the HTTP authorization header in order
37 to authenticate the request against the tracker. 37 to authenticate the request against the tracker.
38 38
39 list 39 ======= ====================================================================
40 :arguments: classname, [property_name] 40 Command Description
41 ======= ====================================================================
42 list arguments: *classname, [property_name]*
41 43
42 List all elements of a given ``classname``. If ``property_name`` is 44 List all elements of a given ``classname``. If ``property_name`` is
43 specified, that is the property that will be displayed for each 45 specified, that is the property that will be displayed for each
44 element. If ``property_name`` is not specified the default label 46 element. If ``property_name`` is not specified the default label
45 property will be used. 47 property will be used.
46 48
47 display 49 display arguments: *designator, [property_1, ..., property_N]*
48 :arguments: designator, [property_1, ..., property_N]
49 50
50 Display a single item in the tracker as specified by ``designator`` 51 Display a single item in the tracker as specified by ``designator``
51 (e.g. issue20 or user5). The default is to display all properties 52 (e.g. issue20 or user5). The default is to display all properties
52 for the item. Alternatively, a list of properties to display can be 53 for the item. Alternatively, a list of properties to display can be
53 specified. 54 specified.
54 55
55 create 56 create arguments: *classname, arg_1 ... arg_N*
56 :arguments: classname, arg_1 ... arg_N
57 57
58 Create a new instance of ``classname`` with ``arg_1`` through 58 Create a new instance of ``classname`` with ``arg_1`` through
59 ``arg_N`` as the values of the new instance. The arguments are 59 ``arg_N`` as the values of the new instance. The arguments are
60 name=value pairs (e.g. ``status='3'``). 60 name=value pairs (e.g. ``status='3'``).
61 61
62 set 62 set arguments: *designator, arg_1 ... arg_N*
63 :arguments: designator, arg_1 ... arg_N
64 63
65 Set the values of an existing item in the tracker as specified by 64 Set the values of an existing item in the tracker as specified by
66 ``designator``. The new values are specified in ``arg_1`` through 65 ``designator``. The new values are specified in ``arg_1`` through
67 ``arg_N``. The arguments are name=value pairs (e.g. ``status='3'``). 66 ``arg_N``. The arguments are name=value pairs (e.g. ``status='3'``).
67 ======= ====================================================================
68 68
69 sample python client 69 sample python client
70 ==================== 70 ====================
71 :: 71 ::
72 72

Roundup Issue Tracker: http://roundup-tracker.org/