--- ../roundup-1.4.19/share/doc/roundup/html/_sources/xmlrpc.txt	2010-10-29 06:36:04.000000000 -0400
+++ share/doc/roundup/html/_sources/xmlrpc.txt	2012-03-10 20:36:31.376606100 -0500
@@ -11,9 +11,16 @@
 limiting. The XML-RPC frontend provides the ability to execute a limited subset
 of commands similar to those found in roundup-admin from remote machines. 
 
-roundup-xmlrpc-server
+There are two ways to access the xmlrpc interface:
+
+  stand alone roundup-xmlrpc-server
+
+  access via the roundup server
+  
+  
+stand alone roundup-xmlrpc-server
 ---------------------
-The Roundup XML-RPC server must be started before remote clients can access the
+The Roundup XML-RPC standalone server must be started before remote clients can access the
 tracker via XML-RPC. ``roundup-xmlrpc-server`` is installed in the scripts
 directory alongside ``roundup-server`` and roundup-admin``. When invoked, the
 location of the tracker instance must be specified.
@@ -23,6 +30,13 @@
 The default port is ``8000``. An alternative port can be specified with the
 ``--port`` switch.
 
+accessing via roundup server
+----------------------------
+In addition to running a stand alone server described above, the
+xmlrpc service is available from the roundup HTTP server. Access it by
+sending text/xml data to the URL for the roundup tracker with the last
+component of the url set to 'xmlrpc'.
+
 security consideration
 ======================
 Note that the current ``roundup-xmlrpc-server`` implementation does not
@@ -108,3 +122,10 @@
         []
         >>> roundup_server.lookup('user','admin')
         '1'
+
+If you are accessing the interface via the roundup HTTP server, a url
+similar to:
+
+  http://username:password@localhost:8000/tracker/xmlrpc
+
+should be used.