on Thu, 17 Jul 2003 13:55:16 +0200 "Andrew Evers" <[EMAIL PROTECTED]> wrote:
> > You implement XML-RPC only in the default plugin, the rest is just a > > framework, a code that does common things and if you support > > different transports, putting the prolog into message isn't common, > > because > > Well, the goal of the package when it was first created was to create > a Java implementation of the XML-RPC specification. This is (as far as > I know) still the main goal. Allow me to cite member of very the same dev team, Ryan: <cite> (...) I am working on abstracting the transport layer so that things like a jabber transport can be plugged in. </cite> > We'd like to make things more accessible > and customizable to developers, but not to the extent that we > encourage people to do things that break interoperability. You don't encourage people to break interoperability, you just ease them to do that :) Besides it's possible to "fix" it with a gate which would be very easy to make using this framework (if it allowed different transports, not mentioning there is already one). For you such extention is 'breaking ineroperability', for me it's an easy way for people to write code that exactly meets their needs. regards, rufio
