Apache XML-RPC is a Java implementation of XML-RPC, a popular protocol that uses XML over HTTP to implement remote procedure calls.
Apache XML-RPC was previously known as Helma XML-RPC.
If you have code using the Helma library, all you should have to do is change the import statements in your code from helma.xmlrpc.* to org.apache.xmlrpc.*.
Apache XML-RPC provides two client classes.
1. org.apache.xmlrpc.XmlRpcClient uses java.net.URLConnection, the HTTP client that comes with the standard Java API
2. org.apache.xmlrpc.XmlRpcClientLite provides its own lightweight HTTP client implementation.
If you need full HTTP support (e.g. Proxies, Redirect etc), you should use XmlRpcClient. If you don't need full HTTP support and are concerned about performance, you should experiment with both XmlRpcClient and XmlRpcClientLite.
On some platforms XmlRpcClient may be faster, while on others XmlRpcClientLite may be faster. Both client classes provide the same interface, which includes methods for synchronous and asynchronous calls.
What is new in this release:
- Eliminated a possible race condition in the ThreadPool. Fixes XMLRPC-162. Thanks to Mark Gertsvolf.
- fix The ThreadPool could create more threads than configured. Fixes XMLRPC-161. Thanks to Mark Gertsvolf.
- fix Weakened the access control in the WebServer class in order to make subclassing easier. Fixes XMLRPC-160. Thanks to James Baldassari.
- fix Improved the handling of HTTP status codes that indicate an error. Fixes XMLRPC-159. Thanks to Brandon DuRette.
- fix Fixed a possible NPE in case of a malformed HTTP request in the WebServer. Thanks to Alan Burlison.
- fix The webserver's connection timeout wasn't applied to the ServletWebServer. Fixes XMLRPC-166. Thanks to Alan Burlison.
- fix A client could prevent other clients from connecting by not sending any data. Fixes XMLRPC-166. Thanks to Alan Burlison.
- fix The platforms default encoding has been used at some point when decoding HTTP headers. Fixes XMLRPC-164. Thanks to Greg Wurth.
Comments not found