Hi Jochen,
I assume that
+) patch 3) and 6) could also go into CVS HEAD of xml-rpc? +) you are a XML-RPC committer .... hint, hint?!
I updated the Maven project
+) to fix the broken link the mail archives +) added a few standard reports
The site can be found at http://www.apache.org/~sgoeschl/xmlrpc/
Cheers,
Siegfried Goeschl
Jochen Wiedmann wrote:
Siegfried Goeschl wrote:
as a casual XML-RPC user I would like to ask who would volunteer to maintain the XML-RPC project?! If we have volunteers we can contact the existing committers to promote an existing contributor to become a committer ... ;-)
I am relatively acticely maintaining a patch that extends xml-rpc. See http://ws.apache.org/~jochen/patches. The problem is, that my direction is questionable: My intention is to extend xml-rpc over the spec, as long as there is a careful separation between things that are covered by the spec (and are enabled by default) and others (which must be explicitly enabled). See below.
Jochen
Apache XmlRpc patch ===================
This is a patch file for Apache XmlRpc, as of 20-Jun-2004. It is available from
http://ws.apache.org/~jochen/patches/ and includes the following changes:
1.) Uses a SAX 2 parser, rather than MinML or another SAX 1 parser. See
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=875
2.) Supports null values by setting XmlRpcClient.isSupportingTypeExtensions(true)
and XmlRpcServer.isSupportingTypeExtensions(true). See
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=908
3.) Replaced the deprecated com.sun.net.ssl classes with javax.net.ssl.
See http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=888
4.) Uses a random, free server port for the test suite, rather than the fixed
ports 8081, etc. See
http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]&msgNo=901
5.) Supports byte, short, long, and float by enabling type extensions. Enabling
these extensions works as in 2.)
6.) Patch for reduced memory use, see http://marc.theaimsgroup.com/?l=xmlrpc-dev&m=108984675831883&w=2
7.) Supports instances of java.io.Serializable by enabling type extensions. Serializable
objects are converted into a byte array, gzipped, and base64 encoded. See
2.) for how to enable type extensions.
