Re: XML_RPC Patch : Nonblocking Requests
| From: | Marshall Roch | Date: | Tue, 02 Dec 2003 22:08:00 +0000 |
| Subject: | Re: XML_RPC Patch : Nonblocking Requests | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-24062@lists.php.net to get a copy of this message | ||
Norman Elton wrote:
I noticed they weren't in the rest of the package. If you're working on the rest, I'll write up docs for mine.Please do. :)
I was toying with the idea of a better PHP Variables <--> XMLRPC Variables code, so that the beginning user doesn't have to worry with creating XML_RPC parameter objects.It's been a few weeks since I've had time to look at XML_RPC, so I might be thinking of something else, but there are helper functions (XML_RPC_encode() and _decode()) that try to guess at the right variable type.
The class would automatically (recursively) convert back and forth. This is where the Incutio implementation (http://scripts.incutio.com/xmlrpc/) really excels. A beginning coder would likely adopt the Incutio implementation for its simplicity.The Incutio version looks cool (only looked at the site). The PEAR XML_RPC package has a problem with memory usage (see bugs), which I think is because of its use of eval(). If we can keep the API the same, and PEAR supports the Artistic License, maybe switching to a more Incutio-like implimentation would solve some problems.
Granted, the PEAR distribution would be backwards-compatible.XML_RPC is used by the PEAR installer, so BC is very important. -- Marshall Roch