also useful to have notifications before an operation--or even
during the operation, if the notification is an end unto itself.
Typically, notifications are named with future tense (DogWillPoop) and
past tense (DogDidPoop or DogPooped) to indicate whether they preceed or
follow the action. Sometimes
On Thu, Aug 28, 2003 at 07:26:25PM -0400, Dan Sugalski wrote:
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 [...]
Only after the action being watched is performed I presume.
Any implementation details?
table for can
be handled with notifications. (And they can tie it in those cases
where a notification is insufficient)
What does this have to do with weak references?
Weak references are just references that aren't part of the root set
and have a destruction notification pending on the thing
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
. 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
