[Tickets #1568] Observer Mechanism Implementation

[bugs@bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/?id=1568
-----------------------------------------------------------------------
 Ticket             | 1568
 Updated By         | Jason Felice <jfelice at cronosys.com>
 Summary            | Observer Mechanism Implementation
 Queue              | Horde Framework Packages
 State              | Feedback
 Priority           | 1. Low
 Type               | Enhancement
 Owners             | 
+New Attachment     | Observer.php
-----------------------------------------------------------------------


Jason Felice <jfelice at cronosys.com> (2005-05-24 05:40) wrote:

Here's an update to my tastes, see what you think:

1) Remove integer contstants, use strings like 'delete' instead.
2) Allow an observer to return false to abort.
3) Remove validateDeletion(), instead app would use notifyObservers() with a
different "message".
4) $manager set by reference in ::singleton().

A couple of thoughts I wonder about:

* I'd prefer ObserverSite:: to Observer_Manager:: as the class name.
* What about using the Memento pattern in the ObserverSite:: and attached
Observer:: instances and not directly talk to DataTree?  That way, whups can
store the memento in the tickets table, for example.