Re: updated channels rfc
| From: | Martin Jansen | Date: | Wed, 03 Mar 2004 16:13:02 +0000 |
| Subject: | Re: updated channels rfc | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-163@lists.php.net to get a copy of this message | ||
On Wed Mar 03, 2004 at 08:4137AM -0500, Greg Beaver wrote:
> 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."
"Everywhere" currently means one machine, to which we have full
access.
> In other words, the PEAR_ChannelService code can't just materialize,
> it's dependent on the backend database implementation currently.
I fail to understand, why there is no way to offer some sort of API
skeleton, to which all third-party implementations have to adhere to.
>It will take a lot of work to redesign pearweb to truly modularize it.
To me this implies that we should find an alternative that can be
realized more easily. Refactoring the PEAR website just because of an
addition to the PEAR installer sounds like breaking a butterfly on a
wheel.
--
- Martin Martin Jansen
http://martinjansen.com/