The xmlrpc interface is currently invoked if the content type
is text/xml. That is insufficient however if we want to allow
other mechanisms (e.g. REST in issue 2550734) which may also
consume xml format data (in addition to json ...).

Every other rpc interface I am familiar with has a single
known url path by which it is invoked.

I suggest applying the attached patch to cgi/client.py to
put the xmlrpc interface at the xmlrpc path under the tracker.

E.G. to use the xmlrpc interface with the demo tracker:

>>> import xmlrpclib
>>> roundup_server =
xmlrpclib.ServerProxy('http://admin:admin@localhost:8917/demo/xmlrpc',
allow_none=True)

and then any of the xmlrpc interface commands can be used.

I am also adding documentation for the xmlrpc.txt file
that describes accessing the interface via the roundup
HTTP server with this patch applied.

When this goes out, the upgrading.txt file should include the following:

==========
If you are using the xml-rpc interface, there is a change
in accessing it. You can not send text/xml data to any
roundup url and get a response, you must use the /xmlrpc
url. For example, if you used to send your xmlrpc request to:

   http://myroundup.com/roundup

you need to change the url to read:

   http://myroundup.com/roundup/xmlrpc

to invoke the xmlrpc handler. This allows us to send xml
data to roundup for other handlers (e.g. REST, SOAP ...)
in the future.

Commited the patches to hg. Also updated Changes.txt and updating.txt.

Patch applied and release done. Closing.