KVO has a mechanism of providing a context which allows avoiding collisions between registering/unregistering/handling KVO code residing in a superclass vs subclass implementation.
Notifications have no mechanism to avoid that.
NotificationController seems like the best place to provide such functionality.
KVOhas a mechanism of providing acontextwhich allows avoiding collisions between registering/unregistering/handlingKVOcode residing in a superclass vs subclass implementation.Notificationshave no mechanism to avoid that.NotificationControllerseems like the best place to provide such functionality.