On Wed, Jul 13, 2011 at 7:53 AM, Vladimir Zlatanov <vlado@dikini.net> wrote:

The key, IMHO, will be the order of execution of the callbacks. In
most, if not all, systems I've used so far, based around such
architecture this was their Achilles heel. Drupal hooks are one
high-profile examples.

The problem stems from the weird abstractions - you either don't know
enough what else is out there, or you know too much. both of which are
bad. Subject-observer while good, has its downsides :(

The other option is to enforce separation of the results of the
callbacks, so that the output is always deterministic.

Cheers,
Vlado


I like the idea, and I think the callbacks can be executed in the order they are defined in the model. Even if it only saves you from writing all the validation boilerplate code seems worth giving a try.
 
_______________________________________________
web-devel mailing list
web-devel@haskell.org
http://www.haskell.org/mailman/listinfo/web-devel