Re: [pear-webmaster] I think your xmlrpc methods are psychic.

Martin Jansen wrote:

On Tue Dec 21, 2004 at 08:0628PM +0200, Steph wrote:

I'm pretty sure it's something to do with caching - everything worked fine up until the night before last, but there were no changes in pearweb in the five days leading up to this (Helgi tells me). Derick cleared the cache last night though at my request, and the problem's still there. Also the PEAR installer's currently b0rked and giving similar error messages, so it seems it's pretty much across the range. Strangely though, package release information, which I also pull in via xml-rpc, hasn't been affected. (That means package.listLatestReleases is working fine at present).

I just cleared the cache and immediately after that did "pear install Config", which resulted in "No release with state equal to: 'stable' found for 'Config'". So it looks like the cache is not involved this time. Very strange. I'm about to leave for the evening, so if someone else knows anything to solve this, that'd be great.

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 :). There must be some kind of race condition when generating the signature file. I will add in some locking, and that should fix it. 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. 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. Greg