Re: info on 2.0?

[Ryan Hoegg]

Andrew Evers wrote:

That said, there are several major changes we have informally planned
for 2.0.  Some of these include:
- abstraction of HTTP transport from XML-RPC processing
- interceptors and introspection
- use of commons-logging, commons-httpclient, and commons-codec internally
   

Well, I've got the commons-logging stuff cooking at the moment. See my other
message for today.
I think we should work on splitting the toplevel package into client and
server packages (although this always plays havoc with CVS).
Yes, and in general we should look at our package structure.  I think we 
should encapsulate any "special" or "optional" subsystems in their own 
packages.  I will do that with the commons transport stuff.

Speaking of transports, any opinions on whether we should generalize the 
transport interfaces to work with the server side as well?  That might 
simplify your servlet stuff.

The SimpleXmlRpcClient needs to leverage the common code in XmlRpc
rather than go off on it's own. I think we should keep a dumb as nails
client in there for people who don't want all the external dependencies
that using the commons libraries implies. This also effects applet
packaging.
+1

I'd also like to continue refactoring the server side of things, making
classes taking internal classes like Runner and Connection out of larger files, and
creating them up with factories instead of calling new directly. This would
greatly aid embedding, and expose some of the power of the XmlRpcContext
stuff I added in the last refactoring.
 

+1

I've also promised to provide a standard servlet embedding for the xml-rpc
classes. Unfortunately the project I have that needs it has been delayed, it
is still coming though.
As a side issue, where is the commons-codec project in CVS? It doesn't
seem to be in jakarta-commons/codec.
Its in the Sandbox.  There have been murmurs about eventual promotion to 
the commons proper, but its still a way off.

One practical effect of this is that the Commons disallows releases from 
the Sandbox.

Now, I think we should start using the target mileston funtionality of 
Bugzilla.  But, I still do not have admin rights.  I think this is why:

> > Pier, the following Apache XML-RPC need Bugzilla admin permissions for
> > XML-RPC:
> > 
> > rhoegg

> [EMAIL PROTECTED] ??? (Ryan Hoegg)

yes
So would someone mind making some milestones and we will start managing 
these 2.0 goals that way? :)

--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net