Re: Framework Development (2)
| From: | Sebastiao Rocha | Date: | Tue, 18 Jun 2002 01:09:01 +0000 |
| Subject: | Re: Framework Development (2) | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-7167@lists.php.net to get a copy of this message | ||
> alexmerz@php.net wrote*:
>
> Sebastiao Rocha wrote:
>> DB_log, its it like (could find in the cvs checkout) ... Im thinking
>> if we have something like jakarta's Log4J
>> (http://jakarta.apache.org/log4j/docs/index.html) ( hum... Log4PHP )
>> that should be VERY cool!!
>
> Feel free to extend PEAR::Log
Better yet. Looking at the MVC code from Jens, I was scratching my
( virtual ) hair thinking how to better handle the DB connections.
The answer was to put it as a persistence pattern.
Then the other problem cames: howto link Model to Controler to View.
Answer a Suject/Observer pattern. If we put the code for S/O pattern apart
from Log we have a lot of space. We will still have Pear Log working, with
very little change. I can do a debugging stuff like Log4J, and can link the
model to controler to view. easy :)
Do I have to make another S/O pattern package with or shall we split the
Pear Log in pieces? :)
S.Rocha