Michael G Schwern <[EMAIL PROTECTED]> writes: > On Thu, Aug 28, 2003 at 07:26:25PM -0400, Dan Sugalski wrote: >> What is a notification system? Well, what it is is a simple system >> that posts an event when a watched resource is changed. We're going >> to watch modification, deletion, addition, and destruction. >> >> How does it work? Simple. When a watched resource does what we're >> watching for (it changes, an entry is deleted, an entry is added, a >> thing is destroyed) we post an event to the event queue. When that >> event is processed, whatever notification routines were registered >> are run. Very simple. >> >> Why? >> >> Because there's all sorts of stuff we need to watch for performance >> reasons. > > My first thought on reading this was it would be rather useful for > debugger watch-expressions.
Notifications are great for all sorts of things. They're classically part of what you want for MVC stuff; whenever the model changes it posts an "I've changed!" notification and any views on it go look at the model and alter the display appropriately.
