Re: updated channels rfc

From: Date: Wed, 03 Mar 2004 03:17:07 +0000
Subject: Re: updated channels rfc
References: 1 2 3 4 5 6  Groups: php.pear.core 
Request: Send a blank email to pear-core+get-156@lists.php.net to get a copy of this message
Hi, The next step in supporting channels will be making pearweb into a distributable package. I've started this work, beginning with a package.xml. The next step is going to be separating out the PEAR-specific content into an easily customizable design. It currently has about 25 dependencies, and so the -a switch is your friend :) (pear install -a pearweb) What I would do to begin is familiarize yourself with the basic structure of pearweb as it currently stands. This will help immensely, as you will see PEAR-only assumptions that won't work for horde, and this will help to separate the content out that needs to be separated. I'm trying to get things organized tonight, but I'm sure it will take many more days before it's ready. I've got many basic things worked out, but there's a huge amount of legacy code to sort through. Now that channels are starting to stabilize with some consensus, I am actively working on the implementation, and you'll see code soon, just have to work out some nitty-gritty details behind the scenes with Pierre and then we can expose the first alpha of the new stuff. You will need to support a /get/ URI, and the XML-RPC that is available in pearweb/include/pear-database.php. Greg Jon Parise wrote:
On Tue, Mar 02, 2004 at 07:14:45PM -0500, Greg Beaver wrote:
What do you mean by protocol? What XML-RPC is needed? This is definitely worth defining clearly. Are you thinking something like <channel> ... <protocols> <implements version="1.2">PEAR</implements> <implements version="1.0">Zzoss</implements> </protocols> </channel> Like that?
Yes, something like that. Put another way, I'd like to know what I would have to do to make pear.horde.org compatible with the PEAR installer. Are there file layout requirements? Do I need to support a /get/ URI?


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