... long drawn out discussion over whether or how to implement a pluggable transport layer ...
*bangs head*
Guys. This can be done with sane XML-RPC request/response objects (think servlets) and an interceptor API, instead of creating N endpoint implementations. This horse has _so_ left the barn. For reference: http://aeolus.cit.cornell.edu/pub/xmlrpc/xmlrpc.html (way way out of date, but look at the interceptor API for reference, the signatures could be condensed with request/response objects; also see example). People who want to tweak the transport without engaging in religious wars can do so without affecting anybody else or forking with respect to endpoints, and having to modify their code to support some one-off client or server API.
Aaron Hamid
