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

From: Date: Sat, 05 Mar 2005 21:34:37 +0000
Subject: Re: [pear-webmaster] making the pearweb kitchen cooler
References: 1 2 3 4  Groups: php.pear.webmaster 
Request: Send a blank email to pear-webmaster+get-3943@lists.php.net to get a copy of this message
On Sat, 05 Mar 2005 16:18:53 -0500 Greg Beaver <cellog@php.net> wrote: > 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 These steps are what we talk about many times and this is a very good solution, for 1.4+, exactly what any other pkg servers do. > 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. This step is basically what can be done now (and what I meant), simple http static files server problems. http://pear.php.net/get/Foo-1.2.3.tgz (and uncompress mode too), it will even work with installers prior to 1.4, still the rpc request request to get the url, can be "fixed" in 1.3.x as well. --Pierre

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