Re: updated channels rfc
| From: | Greg Beaver | Date: | Wed, 03 Mar 2004 13:41:37 +0000 |
| Subject: | Re: updated channels rfc | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-161@lists.php.net to get a copy of this message | ||
Martin Jansen wrote:
I really do not like that particular part of your plan. Distributing the code that runs pear.php.net will make the life of the people that are maintaining the website much harder, because in addition to taking care that the code runs on pear.php.net, they then also will need to take care that it basically runs everywhere else as well. This is not true, my plan was to offer it as-is. However, the main point is that as it currently stands there is no way to separate the logical backend from the visual layout, and this must be done or channels will never work - I have absolutely no interest in doing the same minor changes in both pearweb and peclweb if a bug is found in the channels code. Don't forget about PECL :). The code already has to work "everywhere."The idea I had in mind was to split up the code into several sections, and define them using a couple of package.xml files, but before I do that, I need to get a working package.xml that will install the whole site as it is, and then split things up. In other words, the PEAR_ChannelService code can't just materialize, it's dependent on the backend database implementation currently. It will take a lot of work to redesign pearweb to truly modularize it. Greg