You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rpc-dev@xml.apache.org by ha...@apache.org on 2001/11/07 13:46:34 UTC
cvs commit: xml-rpc/xdocs client.xml server.xml
hannes 01/11/07 04:46:34
Modified: xdocs client.xml server.xml
Log:
Changed /xml-rpc to /xmlrpc in the links to the api-docs.
Revision Changes Path
1.3 +3 -3 xml-rpc/xdocs/client.xml
Index: client.xml
===================================================================
RCS file: /home/cvs/xml-rpc/xdocs/client.xml,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- client.xml 2001/10/31 21:35:13 1.2
+++ client.xml 2001/11/07 12:46:34 1.3
@@ -12,10 +12,10 @@
Apache XML-RPC provides two client classes.
</p>
<ul>
- <li><a href="/xml-rpc/apidocs/org/apache/xmlrpc/XmlRpcClient.html">org.apache.xmlrpc.XmlRpcClient
+ <li><a href="/xmlrpc/apidocs/org/apache/xmlrpc/XmlRpcClient.html">org.apache.xmlrpc.XmlRpcClient
</a> uses java.net.URLConnection, the HTTP client that comes with
the standard Java API</li>
- <li><a href="/xml-rpc/apidocs/org/apache//xmlrpc/XmlRpcClientLite.html">org.apache.xmlrpc.XmlRpcClientLite</a> provides its own lightweight
+ <li><a href="/xmlrpc/apidocs/org/apache//xmlrpc/XmlRpcClientLite.html">org.apache.xmlrpc.XmlRpcClientLite</a> provides its own lightweight
HTTP client implementation.</li></ul>
<p>XmlRpcClientLite is usually faster, but if you need full HTTP support
(e.g. Proxies, Redirect etc), you should use XmlRpcClient.Both client
@@ -59,7 +59,7 @@
<p>If the caller
is interested in the result of the remote call, or wants to be
notified of exceptions, it can pass an object implementing the
- <a href="/xml-rpc/apidocs/org/apache/xmlrpc/AsyncCallback.html">org.apache.xmlrpc.AsyncCallback</a>
+ <a href="/xmlrpc/apidocs/org/apache/xmlrpc/AsyncCallback.html">org.apache.xmlrpc.AsyncCallback</a>
interface to the XML-RPC client class. This interface defines two
methods:</p>
1.4 +4 -4 xml-rpc/xdocs/server.xml
Index: server.xml
===================================================================
RCS file: /home/cvs/xml-rpc/xdocs/server.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- server.xml 2001/10/31 21:42:04 1.3
+++ server.xml 2001/11/07 12:46:34 1.4
@@ -17,8 +17,8 @@
</section>
<section name="XML-RPC Handler Objects">
<p>
- The <a href="/xml-rpc/apidocs/org/apache/xmlrpc/XmlRpcServer.html">
-org.apache.xmlrpc.XmlRpcServer</a> and <a href="/xml-rpc/apidocs/org/apache/xmlrpc/WebServer.html">
+ The <a href="/xmlrpc/apidocs/org/apache/xmlrpc/XmlRpcServer.html">
+org.apache.xmlrpc.XmlRpcServer</a> and <a href="/xmlrpc/apidocs/org/apache/xmlrpc/WebServer.html">
org.apache.xmlrpc.WebServer</a> classes provide methods that let your register and
unregister Java objects as XML-RPC handlers:</p>
@@ -42,9 +42,9 @@
<li>
If you pass the XmlRpcServer an object that implements interface
- <a href="/xml-rpc/apidocs/org/apache/xmlrpc/XmlRpcHandler.html">
+ <a href="/xmlrpc/apidocs/org/apache/xmlrpc/XmlRpcHandler.html">
org.apache.xmlrpc.XmlRpcHandler</a> or
- <a href="/xml-rpc/apidocs/org/apache/xmlrpc/AuthenticatedXmlRpcHandler.html">
+ <a href="/xmlrpc/apidocs/org/apache/xmlrpc/AuthenticatedXmlRpcHandler.html">
org.apache.xmlrpc.AuthenticatedXmlRpcHandler</a> the execute() method
will be called for every incoming request. You are then in full control
of how to process the XML-RPC request, enabling you to perform input and output