object-oriented XML_RPC

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'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? How about creating client and server packages to coexist with the current one instead of replacing it and breaking backwards-compatability? 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). 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. -- Marshall Roch