Kudos to all the committers of this project, the changes were fairly simple. This is due to a number things, a desire to keep the architecture fairly simple, maintaining JDK 1.1 compliance and using MinML. Special thanks to John for this last.
This is the gist of the modifications. I removed the superclass (XmlRpcClient) and copied a couple of methods across and removed the superclass of LiteWorker (Worker) and copied some methods. I think that I also trashed the Async code. There are minor changes to XmlRpc.java (removing "properties"), other than that, you need Base64.java, ServerInputStream.java and XmlRpcException.java which compile unchanged. I think that there also some supporting classes that we had already created (StringTokenizer?), maybe others. References to URL and associated exceptions have been removed, if we need these to match a new interface (likely) we will need to create substitutes.
If anyone else has an immediate interest in this code, let me know. I'll be testing over this week, the goal is to get it on the iPaq/Jeode.
Jim
On 2002.11.03 17:30 Ryan Hoegg wrote:
Jim,
Sounds great! I think the status now is that we are keeping the XmlRpcClient class but pulling out the salient bits into more focused classes. The XmlRpcClient class will depend only on interfaces, and implementations for those interfaces will be distributed in separate packages to facilitate building JARs that are tailored to specific users. This is all still pre-alpha of course, and we weclome further discussion.
Your's looks like a great use case to help us with the design direction here. If you search the archives for the "HttpClient Integration" thread you can read a lot of the recent progress in this area, with the bulk of the tangible code coming from Andrew Evers.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Jim Redman wrote:
I only vaguely remember the discussion of adding an interface for the client. Can someone provide a quick synopsis and the status?
It just became relevent to me because I have a need for a CLDC client. kxmlrpc assumes MIDP (HttpConnection). Since MinML is (just about) CLDC compliant, if I can easily convert the XmlRpcClient to CLDC I may have a good solution. If I'm going to do this, I might as well make it compliant with the forthcoming interface.
Jim
-- Jim Redman (505) 662 5156 http://www.ergotech.com
