Re: NSDistributedNotificationCenter
Re: NSDistributedNotificationCenter
- Subject: Re: NSDistributedNotificationCenter
- From: Chris Kane <email@hidden>
- Date: Wed, 20 Feb 2002 16:32:47 -0800
On Saturday, February 16, 2002, at 11:30 AM, Justin Wood wrote:
I have been trying to use the distributed notification center to pass
information between a client and server application. The chatter
between them is simple event based so I opted for this over a
Distributed Objects style of IPC.
Everything works just fine, for a while, after the chatter gets to a
certain level, maybe > 10-15 messages per second, the notifications
just seem to disappear, completely. Once one is dropped, no more seem
to pass through. This leads me to the assumption that somewhere a queue
is getting filled up, freezes, and doesn't know what to do.
In 10.0 and 10.1, if the notification server gets an error, any error,
in trying to send a notification to a client, including port queue full,
the server purges all knowledge of that client. This is arguably a bug,
but it does manage to keep people from using distributed notification as
a high-volume communication channel, which it is not supposed to be (it
can impact the system performance quite a bit).
In the next OS release, the situation has been improved somewhat I
think; I believe it will wait longer for space to become available in
the queue, and I think the client-purge was eliminated, but I think the
server might still decide to toss some notifications on the floor in
high-volume situations. As an example, we can't have the server
potentially using an open-ended amount of memory to keep notifications
queued for clients which may have permanently gone out to lunch.
Chris Kane
Cocoa Frameworks, Apple
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.