Re: Major Channels RFC update

From: Date: Thu, 13 May 2004 08:48:17 +0000
Subject: Re: Major Channels RFC update
References: 1  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-315@lists.php.net to get a copy of this message
Zitat von Greg Beaver <greg@chiaraquartet.net>:
Hi all, I just spent a substantial amount of time updating the channels RFC, as I have been spending a lot of time actually coding the thing, and that necessarily changes what is required. Pierre-Alain and I had a good planning session on what is needed for mirrors, so I added some of that stuff too. Comments will be good. I think we've found a solution to the "what can the server do" problem - list it in the channel.xml file, so no querying of the server is necessary except for testing purposes. I think you'll find that things make a bit more sense, some of the superfluous stuff was removed. Anyways, here's the address: http://pear.dnsalias.net/index.php?area=PearCore&page=PearChannels Comments are not only appreciated, they are essential to getting this right. I will be finishing up the basic code this week, and Pierre will take over while I'm out of town, we plan to have a fully working implementation by Linuxtag with any luck.
Looks very nice and complete, great work! One suggestion, your inline comment sounds like you don't like this one either ;-): <protocol type="get" version="1.0"/> <!-- better name for this than "get"? "get" means that http://pear.php.net/get/Package-1.0.tgz is supported --> I think this is confusing because you also have type="xmlrpc", so I would assumet the type="get" is relating to HTTP GET requests. <protocol type="get" version="1.0">get</protocol> would be better IMO, because it would allow for future <protocol type="get" version="1.0">list</protocol> or <protocol type="post" version="1.0">upload</protocol> Jan. -- Do you need professional PHP or Horde consulting? http://horde.org/consulting/

« previous php.pear.core (#315) next »