Re: making the pearweb kitchen cooler
| From: | Greg Beaver | Date: | Fri, 04 Mar 2005 17:04:12 +0000 |
| Subject: | Re: making the pearweb kitchen cooler | ||
| References: | 1 | Groups: | php.pear.webmaster |
| Request: | Send a blank email to pear-webmaster+get-3934@lists.php.net to get a copy of this message | ||
Pierre-Alain Joye wrote:
My next step is to make the pkg downloads static. At least the first try. That may require some changes in the installer. Mostly all cases can be manage using static files or links on the server. If one fails, the installer will use a rpc query to get a a download url or an error.This is a terrible way to implement this - what we need to do is provide a bunch of static information in xml format about each package and release, and use hyperlinks in the xml so that the installer can follow them to do dynamic stuff client-side. Guesswork was the hallmark of what stinks about 1.3.x and its error messages. I've got a nearly finished working concept of a REST-based interface that is currently dynamic, but could easily be modified to be static. I will see what I can do to staticize the stuff I already have. It would require a few scripts to process existing releases, but I already have practice doing this, so that shouldn't be a problem. Greg