Hi,
I'm in the process of integrating an XmlRpcClient into our own
"Connection Pool" type classes and was intending to use an Apache commons
HttpClient and a "modified" XmlRpcClient until I noticed the XML-RPC 2.0
library has introduced the concept of pluggable transports.
1) I notice that the XML-RPC class library has changed significantly for
2.0. Can you tell me when will 2.0 is likely to be released (I've donwloaded
the 2.0 a1 code from CVS).
2) I would like to pool XmlRpcConnection objects (which contain
XmlRpcClients) but as the URI for each request could be different I was
intending to use an Apache Commons HTTP client (which allows the URL to be
specified when constructing each PostMethod object and the HttpClient object
to be re-used.
I notice the XML-RPC 2.0 libarary now uses the commons-http client but there
is no setUrl type method on the new CommonsXmlRpctransport class.
Is a setUrl method this likely to be introduced?
3) Is the CommonsXmlRpcTransportFactory class missing - or am I
misunderstanding something?
Thanks
Richard
Richard Grimshaw
PPAS Principal Engineer
Schlumberger
