On Sat, Jun 14, 2008 at 8:52 PM, dream cat7 <[EMAIL PROTECTED]> wrote:
> Seeing notifications from outside: > [...] > Sometimes 2 process are > communicating And one of them is launching / closing multiple times during > the session (e.g. sending kill message as NSNotification). You refer to NSNotification many times in your post, but NSDistributedNotification only once or twice; I assume from the context that you always mean the latter. > Indeed I am not shifting around any large volumes of data at the moment, it > is maybe 10 or so application preferences settings, with a 2-3 of data > objects which are archived with NSCoding/NSArchiver protocol. However as my > application becomes more enhanced, there may be significantly more such > "medium size" data object. Why not put the data files somewhere else, i.e., Library/Application Support? Then you can distinguish between changes in preferences and changes in data, break down the atomicity of your data as far as you like, easily write Spotlight plugins, etc. > With a launchd - administered process they can be started at any time. But > is it reasonable to believe that the daemon can start running before the > NSNotification centre and then some time after it started that it can > register with the notification centre when it becomes available ? I don't know, but I'd imagine that if you call +[NSDistributedNotificationCenter defaultCenter] before the center exists, it will be created. Hamish _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
