Re: object-oriented XML_RPC

Marshall Roch wrote:

I want to use XML_RPC, but it's a very messy looking package (i.e. $GLOBALs all over the place and repetitive function names like XML_RPC_ee and XML_RPC_xh). I think it'd be nicer as a class, and even perhaps as two packages: XML_RPC_Client and XML_RPC_Server.

I've never followed the story on XML_RPC, it appears it was grabbed from some other source, and thown into PEAR very early (probably to use with the Installer).. It is a bit of a mess, and AFAIK it doesnt have a maintainer who loves it :).. - It just works as is.. and I dont think anyone got excited enough to fix it when it wasnt broken... *and also when theres a php extension that does the same thing...

I'm going to move it into a class for my own use. Is this something that would be possible to get into PEAR, or is the lack of backwards-compatability too big of a problem?

The pear installer relies on this package, so BC is very important here.. How about creating client

and server packages to coexist with the current one instead of replacing it and breaking backwards-compatability?

I think they are 2 classes in there server and client... - that file should really be broken up into it's constituant classes.... -

Finally, XML_RPC needs some basic documentation, or at least something that says it's based off of the usefulinc code (found in the archives, I haven't confirmed that for myself yet).

That would be nice..... :)

I'm still new to the whole PEAR thing, so maybe my ideas aren't possible due to the way PEAR works. Let me know whether it's something I should pursue.

Contact Sthe maintiner (Stig) Directly - and put in the subject 'Maintaining XML_RPC' ... he's a little busy.. but will get back to you.. He's the one you should really get comments from.. Regards Alan

-- Marshall Roch