best practice: delegate vs NSNotification

[vertine]

hi, i have a dilemma. I have a UIView that is userInteractionEnabled and recieves events from

- (void)touchesBegan:(NSSet *)touches withEvent:(UIEvent *)event

however, i also have a class that is a Mediator(puremvc, if you know it) that has been assigned this view as its viewComponent. I would like this mediator to know about the touches to the uiview. What is the best way to pass the NSSet and the UIEvent? currently i made a custom protocol of the UIView and had the Mediator conform...but then i started thinking about NSNotifications, etc...any thoughts on this?

[hello24]

Don't use NSNotification unless your coupling is very loose (or non-existent) or you need to let multiple object know about the event.

[macoholic]

Notifications are generally a brodcast system.
Delegates are helpful in case of tightly coupled components....

On a personal front,When I have a loosly coupled components or I need multiple objects to be notified about an event I use Notifications.

In all other scenarios it's delegates that I love!!

Macoholic

[MikaelBartlett]

Can I send messages to my delegate running on the main thread when running in a separate thread?

[harrytheshark]

Originally Posted by MikaelBartlett

Can I send messages to my delegate running on the main thread when running in a separate thread?

Yes you can, by using performSelectorOnMainThread: