Re: PSClientDelegate
Re: PSClientDelegate
- Subject: Re: PSClientDelegate
- From: "Stephen J. Butler" <email@hidden>
- Date: Fri, 3 Dec 2010 18:37:21 -0600
On Fri, Dec 3, 2010 at 5:38 PM, Daniel DeCovnick <email@hidden> wrote:
> For that matter, I'm not sure when to use these methods, versus when to register for the PSFeedRefreshingNotification, PSFeedEntriesChangedNotification, etc.
In general, a framework that sends notifications will also, as a
convenience, send a repacked form of those notifications to its
delegate. That's just to save time, the idea being that a delegate
closely associated with an object will also want to repsond to its
notifications. But there's no advantage/disadvantage to choosing the
delegate methods over the notifications.
The only time it's required to use delegate methods over notifications
is if a response is required. Notifications can't return values, but
delegates can. For example, the NSWindowDelegate windowsShouldClose:
message... you can't do that with a notification.
As far as PubSub is concerned, no experience myself (and that
framework reference is horrid). Did you see the Guide? I don't think
it covers the callbacks you listed, but it does have some useful
information:
<http://developer.apple.com/library/mac/#documentation/InternetWeb/Conceptual/PubSub/Introduction/Introduction.html>
As far as the unknown ones... personally I'd just stick logging
statements in there and see what happens. Intuition says it's just an
easy way to get a 'diff' when the feed is updated.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden