Hi,

Just some feedback on the API. :)
I'm in the situation that I manually need to create/encode/decode and
dispatch XML-RPC requests and responses. Encoding/decoding stuff was a
snap, but it would be nice if XmlRpcRequestProcessor had a public default
constructor. Right now it's protected and I cannot think of a good reason
for that. I need to get the XmlRpcServerRequest from an incoming byte[]
blob, and this seemed to be the Right Way.
I'd also like to see public constructors added to the other classes for
consistency; right now it's a rather unpretty mish-mash and not quite
clear which classes are fit for public consumption and which are not.

thanks,
Holger

Reply via email to