Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6650353
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 26, 20262026-05-26T00:52:58+00:00 2026-05-26T00:52:58+00:00

I am writing a component (e.g. VeryLongJobExecuter ) in Objective C. I want this

  • 0

I am writing a component (e.g. VeryLongJobExecuter) in Objective C.

I want this VeryLongJobExecuter to be able to notify other objects (one to many) when its job is finished, and execute a common method, e.g. (jobExecuted).

I am thinking to store the reference of these delegates in either NSArray/NSSet, and iterate the delegates and call the method.

Or should I use Notification instead?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-26T00:52:58+00:00Added an answer on May 26, 2026 at 12:52 am

    The reason that we have notifications is so that you don’t have to keep a reference to every other object that might care about an event. Don’t re-invent the wheel.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm writing a logging component and one of my methods I want to implement
I'm writing and testing a ClassLoader component, which can be instantiated many times, with
I'm writing a WPF application that uses a component, and this component returns a
I'm writing a custom compound control that extends RelativeLayout. Inside this component, there is
I'm writing a component that I would like to be able to use in
I am writing my own Joomla component (MVC), its based heavily on the newsflash
I'm writing an app where one component is a checklist screen. The checklist has
I'm writing a .NET component to be used both by other .net clients and
I am writing a component and its skin. The skin has a selected state
I'm writing a native iPhone app that contains a UIWebView component. This component accesses

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.