|
|
Posted by Rik Wasmus on 09/06/07 14:09
On Thu, 06 Sep 2007 15:14:54 +0200, <ptdorf@gmail.com> wrote:
> the idea is that in a mvc-framework-like application, new modules
> (controllers) interact (by adding or redefining) the behavior
> (methods, actions) of existing ones. each part of the system should be
> able to reach and mess each other (if needed).
>
> for instance, an audit module. you dont need it in every site but in
> some its essential. so when you install that module, it should be able
> to attach himself to some modules (you may choose which ones in the
> admin settings) and from them on every time some method in some
> controller is called, the audit makes sure that that action, user,
> date and data is tracked.
Sounds more like an Observer pattern is needed? No screwing with classes,
just enforce an 'observable' interface unto classes in need of observing,
and add the right Observers to it?
--
Rik Wasmus
Navigation:
[Reply to this message]
|