Re: Re: XML/RPC/Cached_Server ?

> You need 2 caches anyway. One for the client and one for the > server, [...] I agree with you. But I work on a project where I don't control the client side (maybe the XMLRPC call will not be written in PHP...). I only want a rock solid XMLRPC server with good perfs... even if the client side is poorly written. > [...] both being classic cache usages... Fail to see the problem > or needs for extra packages, classes or other similar things. I don't agree with you on this particular point. If you want to make an "easy to use" system but flexible (cache only a few functions call and not all of them), you have to parse the request to get the called function name, you have to generate an id automatically (with a good hash of the XML request...). So the cache on a XMLRPC server is not classic. The pearweb code is a good example about that (see xmlrpc.php file). So this "extra class" is not a trival thing and, IMHO, it would be a good thing to add it in the PEAR/XML/RPC package (it would be a good reason to choose the PEAR version and not the sourceforge one) Regards, -- Fabien MARTY fabien.marty@free.fr