Howdy,
This has come up in conversations with users that I have had off list. I think for 2.0 I would like to create an applet subproject and migrate the core to Java 1.2. There are several opportunities for modularizing the code that I'd like to explore; your MinML-RPC project might fit right in if we structure things right. I'd like to be able to deliver server-only and client-only jars as well as allow alternate transports seamlessly by adding a jar to the classpath. Finally, I'd like to move away from the static base class XmlRpc that we have now to something using composition.
Hopefully I can make time soon to get started!
I'd be glad to help with this and other XML-RPC needs. I'm just getting acquainted with this component's implementation, and some of the code looked specifically maintained for JDK 1.1 systems, hence my original question of whether that was still the policy. ;)
Yoav Shapira
Well, before I commit to Java 1.2 Collections, I'd like to explore the possibility of doing away with Vector and List, Hashtable and Map. Why not create some semantically meaningful interfaces of our own that could then be backed by implementations that adhere to whatever JDK we want? What do we gain by using Collections?
I'm thinking something like:
XmlRpcConnection connection = new XmlRpcConnection("192.168.1.1");
XmlRpcRequest request = new XmlRpcRequest("sample.multiply");
request.addParameter(4);
request.addParameter(8);XmlRpcResponse response = connection.execute(request); int answer = ((Integer) response.getValue()).intValue();
It would be trivial to create an XmlRpcArray that contained the responses and provide Java 1.2 stuff in a wrapper or helper class (like Iterators). Something similar could be done with XmlRpcStruct.
Thoughts? -- Ryan Hoegg ISIS Networks http://www.isisnetworks.net
