Re: [pear-webmaster] making the pearweb kitchen cooler

From: Date: Sat, 05 Mar 2005 21:18:53 +0000
Subject: Re: [pear-webmaster] making the pearweb kitchen cooler
References: 1 2 3  Groups: php.pear.webmaster 
Request: Send a blank email to pear-webmaster+get-3942@lists.php.net to get a copy of this message
Pierre-Alain Joye wrote:
So if you and Greg object on these changes, let forget it. I do not have the time to argue about such obvious things.
It may be language barrier, I only object to oversimplifying things. Here is the way I would like things to work: Developer X releases package Foo 1.2.3 pearweb processes the release, and creates/updates a tree of xml files http://pear.php.net/rest/package/list.xml - package list, which has hyperlinks to each package's static xml info.xml http://pear.php.net/rest/package/Foo/info.xml - package info for Foo, which has hyperlinks to each release http://pear.php.net/rest/package/Foo/releases/version1.2.3/info.xml - contains download url or urls http://pear.php.net/rest/package/Foo/releases/version1.2.3/package.xml - contains the package.xml then it saves the releases themselves: http://pear.php.net/download/Foo-1.2.3.tgz http://pear.php.net/download/Foo-1.2.3.tar http://pear.php.net/download/Foo-stable.tgz (symlink) http://pear.php.net/download/Foo-stable.tar (symlink) Everything has its own unique url, which is a mainstay of rest, and the scalability of http can be used to distribute load properly. If every package had this information, it would be possible to simply follow hyperlinks and use them to retrieve all needed information on downloading packages statically. It would even allow complete mirrors to be made using rsync - no database content needed. Greg

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