I've been thinking further about this issue. If we decide to go ahead and make an XmlRpcClient interface, we either have to decide to use some NonImplementedException framework for the features of the interface that XmlRpcClientLiteImpl does not implement, or we need to use an abstract class with the bare minimum for the root interface and inherit XmlRpcClientWithMoreHttpFeatures from it.
Are there other features XmlRpcClient provides now that XmlRpcClientLite does not, like multithreading? If so, these should be addressed as well. Thoughts? -- Ryan Hoegg ISIS Networks
