Inherits from: NSNotificationCenter : NSObject
Package: com.apple.yellow.foundation
A table of objects that want to receive notifications, the notifications they want to receive, and identifying strings they are interested in.
Each machine has a default distributed notification center. You typically don't create your own.
defaultCenter | Accesses the default notification center. |
addObserver | Registers an object to receive a notification with a specified behavior when notification delivery is suspended. |
postNotificationName | Creates and posts a notification. |
An NSDistributedNotificationCenter object (or simply, distributed notification center) is a notification center that can distributed notifications to tasks other than the one in which the notification was posted.
The distributed notification center notifies all observers of notifications meeting specific criteria. This information is encapsulated in NSNotification objects, also known as notifications. Client objects register themselves as observers of specific notifications posted by other objects. When an event occurs, an object posts an appropriate notification to the distributed notification center. (See the NSNotification class specification for more on notifications.) The distributed notification center dispatches a message to each registered observer, passing the notification as the sole argument. It is possible for the posting object and the observing object to be the same.
Each task has a default distributed notification center that you access with the defaultCenter class method. There may be different types of distributed notification centers. Right now there is a single type-NSLocalNotificationCenterType. This type of distributed notification center handles notifications that can be sent between tasks on a single machine. For communication between tasks on different machines, use Distributed Objects.
An object registers itself to receive a notification by sending the addObserver method, specifying the message the notification should send, the name of the notification it wants to receive, the identifying string to match (the anObject argument), and the behavior to follow if notification delivery is suspended. Because the posting object and the observer may be in different tasks, notifications can't contain pointers to arbitrary objects. Therefore, NSDistributedNotificationCenter requires notifications to use an NSString as the anObject argument. Notification matching is done based on this string, rather than an object pointer. You should check the documentation of the object posting the notification to see what it uses as its identifying string.
There are four different types of suspension behavior, each useful in different circumstances:
NotificationSuspensionBehaviorDrop
When a task is no longer interested in receiving notifications
immediately, it may suspend notification delivery. This is often
done when the application is hidden, or is put into the background.
You suspend notifications by invoking setSuspended with an argument of true
on
the distributed notification center.
While notifications are suspended, the notification server
handles notifications destined for the task that suspended notification
delivery according to the suspension behavior specified by the observers
when they registered to receive notifications. (See the table above.)
When the task unsuspends notification delivery, all queued notifications
are delivered immediately. Note that a notification destined for
an observer that registered with NotificationSuspensionBehaviorDeliverImmediately
will
automatically flush the queue as it is delivered, causing all queued
notifications to be delivered at that time as well.
If an object posting a notification wants to ensure that all
observers receive the notification immediately (for example, if
the notification is a warning that a server is about to shut down),
it can invoke postNotificationName with
a deliverImmediately argument of true
.
The notification center will deliver the notification as if the
observers had registered with NotificationSuspensionBehaviorDeliverImmediately
.
There are four different types of suspension behavior, each
useful in different circumstances.
Suspension Behavior | Description |
NotificationSuspensionBehaviorDrop |
Drops notifications observed with this behavior when the observer suspends notifications. |
NotificationSuspensionBehaviorCoalesce |
Coalesces notifications observed with this behavior, such that only the most recent notification is delivered when notification delivery is resumed. |
NotificationSuspensionBehaviorHold |
Holds all notifications on the notification server for later delivery when notification delivery is resumed. |
NotificationSuspensionBehaviorDeliverImmediately |
Delivers matching notifications immediately. This also
flushes the queue of undelivered notifications-the behavior is
as if the receiving application had momentarily called setSuspended with
an argument of false , then immediately
after all notifications are delivered, called setSuspended again with an argument
of true . |
- Accessing distributed notification centers
- defaultCenter
- notificationCenterForType
- Adding and removing observers
- addObserver
- Posting notifications
- postNotificationName
- Suspending and enabling notification delivery
- setSuspended
- suspended
public static NSNotificationCenter defaultCenter()
public static NSDistributedNotificationCenter notificationCenterForType(String type)
public void addObserver(Object anObserver, NSSelector aSelector, String notificationName, String anObject, int suspensionBehavior)
When
a notification of name notificationName with
the identifying string anObject is
posted, anObserver receives an aSelector message
with this notification as the argument. The method for the selector
specified in aSelector must have
one and only one argument. If notificationName is null
,
the notification center notifies the observer of all notifications
with an identifying string matching anObject.
If anObject is null,
the notification center notifies the observer of all notifications
with the name notificationName. The suspensionBehavior determines
how the notification center handles notifications when notification
delivery has been suspended. Here are the possible values:
NotificationSuspensionBehaviorDrop
See Also: postNotificationName
public void postNotification(String notificationName, String anObject, NSDictionary userInfo, boolean deliverImmediately)
The userInfo dictionary is serialized using the NSArchiver class, so it can be passed to another task. In the receiving task, it is deserialized using NSUnarchiver. This imposes some restrictions on the objects that can be placed in the userInfo dictionary. See the NSArchiver and NSUnarchiver documentation for details.
Posting
with deliverImmediately set to false
allows
the normal suspension behavior of the observers to take place. If deliverImmediately is
set to true
, the notification is
delivered immediately to all observers, regardless of their suspension
behavior or suspension state.
See Also: - encodeRootObject: (NSArchiver) + unarchiveObjectWithData: (NSUnarchiver)
public void setSuspended(boolean suspended)
true
, and resumes immediate notification
delivery when set to false
. Distributed
notification centers enable or suspend notification delivery on
a per-task basis. When a task suspends notification delivery, notifications
are delivered according to the suspension behavior of the observer.
When delivery is not suspended, notifications are always delivered
immediately. See "Suspending Notification Delivery" in the class introduction
for more information. See Also: addObserver, postNotificationName
public boolean suspended()
true
if
the notification center is delivering notifications for this application
according to their suspension behavior, false
if
it is delivering them immediately.