Re: XML_RPC_Easy (pre)proposal

Fabien MARTY wrote:

- XML_RPC2, which is a biggest thing because it replaces XML/RPC - XML_RPC_Easy, which is only an little additional layer and which uses and depends on the well tested XML/RPC stuff If XML_RPC2 is available in a few days (weeks ?), I completly agree to drop my proposal. But if there are some big delays again.....

XML_RPC2 -- the code -- is available right now: http://pear.sergiocarvalho.com/XML_RPC2 It's in production usage in my systems, with pretty heavy loads. As far as I'm concerned, it's reasonably solid -- at least beta quality. XML_RPC2 -- the PEAR package -- may never be available. I'm afraid along the last year, this package proposal has revealed PEAR's major flaw: PEAR has no mechanism in place to prevent package leads from freezing development on a package. There are a multitude of reasons that may cause a lead to freeze a package's evolution, from active anti-social behaviour, to simple lack of time (Dan falls in the latter). PEAR can't correct these faults, or corrects only after inane ammounts of time and political effort. As far as I'm concerned, I'm not producing any more efforts to get the package in. One full year is long enough. The code remains LGPL, so anyone is free to pick it up and climb the long ladder to PEAR acceptance. I plan to take some time and develop xml-rpc for Services_webservice. Regards, Sérgio