Re: Re: XML_RPC Server Debug info

Mark Mitchenall wrote:

I have not had time to work on XML_RPC recently, but things are in the works. The changes I've been planning to make will be fairly drastic (no BC break, though), so it might be a good idea to move that into a branch, or to make a branch for 1.0.4 so we can release small things like this right away.

Sounds good. Out of interest, what changes where you planning?

The code as it stands is rather messy, because of all of the globals (a lot of which should really be constants) and functions not in classes. I just finished moving all of the standalone functions into the base class, so I will commit that as soon as it's tested. I'd also like to add support for xmlrpc-epi, like PEAR/Remote.php has. If the C extension is present, it should use that instead, to take advantage of the extra speed.

Mark, if you create a patch, I don't have a problem with it being committed.

No problem... I'm just working on the patch now and will test it out with a project we're working on at the moment.

XML_RPC is a core package, so make sure it also works with PEAR. Apply your patch to /usr/lib/php/XML/RPC.php (or wherever the PEAR files are on your system), then run "pear clear-cache && pear list-all" to make sure it still works as expected.

Can anyone else advise on the best way to handle CVS?

In what way?

I mean creating branches either for experimental development or 1.0.4 so we can still apply patches like yours after I commit these biggish changes. -- Marshall Roch