Re: [pear-webmaster] I think your xmlrpc methods are psychic.
| From: | Pierre-Alain Joye | Date: | Wed, 22 Dec 2004 14:46:56 +0000 |
| Subject: | Re: [pear-webmaster] I think your xmlrpc methods are psychic. | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.webmaster |
| Request: | Send a blank email to pear-webmaster+get-3625@lists.php.net to get a copy of this message | ||
On Tue, 21 Dec 2004 16:37:54 -0500
greg@chiaraquartet.net (Greg Beaver) wrote:
> It's not the cache. There is a separate cache for xml-rpc
> signatures, it is located in PEAR_TMP_DIR /
> pear-database.php.index. Delete this file and it will work again.
> Stupid piece of crap file :).
Confirmed here. It's not the cache (signature cache). I'm still
wondering why we do not simply generate this file on update and
once. Testing a script update right now.
> FYI, I plan to implement a rest-based API for PEAR. Then we can
> ditch the stupid xml-rpc signature crap, and xml-rpc altogether.
> HTTP caching is much more efficient and robust than all this
> custom junk.
I fail to see what REST brings right now but the http caching?
> Implementing who's-who would be really, really easy. However, I
> wonder if there is a secure cert for pear.php.net? This would be
> a good use for donated funds, so that https://pear.php.net can
> be
> used with HTTP auth to do secure stuff. This will even allow
> remote upload of releases, and remote validation, and so on.
That and a 3rd certification and auth tool is planed. This tool will
solve the privacy issues as well as the user will define themselves
what they allow or not, where, ... The plan is to use xipe, if
possible. I'm still reading the features and specs, a bit more in
the next days.
--Pierre