[ http://issues.apache.org/jira/browse/XMLRPC-75?page=comments#action_12361451 ]
Walter Mundt commented on XMLRPC-75: ------------------------------------ I am sorry if my descriptions are insufficient. I am not sure what you are saying in your last sentence, but in case you would like more information I will try to answer the issues you raise. a) This is correct. Other languages to implement this sub-protocol. I did not link to the pages specifically concerned with this before; here are those links (in alphabetical order by language): C/C++: http://xmlrpc-c.sourceforge.net/doc/libxmlrpc_server.html#systemmethod .NET/C#: http://www.xml-rpc.net/faq/xmlrpcnetfaq.html#3.5 PHP: http://www.php.net/manual/en/function.xmlrpc-server-add-introspection-data.php Python: http://docs.python.org/lib/simple-xmlrpc-servers.html (see register_introspection_functions) and http://docs.python.org/lib/serverproxy-objects.html The second Python link provides a very good description of the three functions this patch is concerned with implementing. b) Also correct. However, what it does with introspection is quite different; rather than using it to implement a simple named method call operation, it essentially translates remote introspection requests into local Java reflection API calls. > Introspection Patch for XML-RPC, current to SVN 2005-12-29 (r359943) > -------------------------------------------------------------------- > > Key: XMLRPC-75 > URL: http://issues.apache.org/jira/browse/XMLRPC-75 > Project: XML-RPC > Type: New Feature > Components: Source > Versions: unspecified > Reporter: Walter Mundt > Attachments: IntrospectionExample.java, xmlrpc-2.0-beta-introspection.patch > > I've taken Aaron Hamid's Introspection patch (which was in turn derived from > the one here: > http://xmlrpc-c.sourceforge.net/hacks/helma-xmlrpc-introspection.diff ) and > basically rewritten it to work with the current XML-RPC library. > I tried to set it up so that it followed the existing coding style as much as > possible, and would not break any existing applications. For example, when I > needed a list of handlers supported by a particular mapping, I added a new > interface XmlRpcListableHandlerMapping that provides this information, made > the default handler implement it, and designed my code so that if it were not > implemented by a handler in use, everything would work except the > system.listMethods functionality that relies on it. > I hope you will be able to integrate this code into the next version of the > library; please contact me with any questions or issues. I will be attaching > the patch to this issue if I can so that the problem with his previous patch > will not occur. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira