Ted Leung wrote:
On Sep 26, 2005, at 9:03 AM, John Anderson wrote:
Phillip J. Eby wrote:
Well, you can disable notifications *during* notifications. That's
the simplest way to avoid cascading. In point-to-point
subscription systems (like peak.events), you can also use the trick
of removing the current callback from the subscriber list when
calling it, so other subscribers will see events generated by that
callback, but the callback itself cannot receive events that it
generates itself.
I tried to disable notifications during notifications, however this
only works with our synchronous notifications, not our asynchronous
ones -- which is the problem I first raised.
What changes did you make to disable notifications? The code that I
have now controls the notification stuff in one place, so it should
be possible to disable notifications before they get delivered.
Technically I don't disable notifications, I just don't dirty blocks
when I get a notification that I want to ignore.
Ted
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
