Re: making the pearweb kitchen cooler

From: Date: Fri, 04 Mar 2005 22:02:19 +0000
Subject: Re: making the pearweb kitchen cooler
References: 1 2 3  Groups: php.pear.webmaster 
Request: Send a blank email to pear-webmaster+get-3936@lists.php.net to get a copy of this message
Pierre-Alain Joye wrote:
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.
It's not a terrible way to implement things. This is the safest way to download data that _never_ changes. It's almost working now, I have ran tests using the current packages, no error. I will run another battery of tests this weekend.
Pierre, this is infuriating. You can't develop a huge thing like this completely in private without any outside input and expect it to satisfy anyone but yourself. PEAR is (or was) a collaboration for a reason. Do you even know what REST *is*? It's the same thing that you're describing, but not as inflexible. You have xml files sitting on the server, or dynamically generated - the client doesn't care which, only the protocol matters. Linking between xml information is performed using xlink, a W3C standard, so that clients can choose and pick. For instance, package PEAR would have a xml at a specific location. This would contain hyperlinks to a release list, which would contain hyperlinks to package.xml for each release. A client could use the release list to determine which release to download in the exact same manner as package.getDownloadURL, and grab the download url from the release list for that package (another hyperlink). All of the dynamism is performed on the client-side, and http caching guarantees that clients will only retrieve the full page once. Server loads would diminish to practically zero. It's a much better solution than the guesswork you described. Greg

« previous php.pear.webmaster (#3936) next »