Home > Articles > Home & Office Computing > Mac OS X

  • Print
  • + Share This
Like this article? We recommend

Like this article? We recommend

Fast Proxies

Fast Proxies

When you send a message on Objective-C, you call a runtime library function that finds the function used to implement the corresponding method. With the NeXT runtime, this is objc_msgSend(), which both looks up and calls the method function. With the GNU runtime, you call objc_msg_lookup() and then call the returned function yourself.

Typically, this lookup follows a fast path, either finding it in a cache or in a sparse array structure (or linked list on the NeXT runtime), mapping selectors to methods for a given class. When this fails, traditionally a forwarding function is called.

The forwarding function is horrible code which, fortunately, most developers never need to go near. It uses the method signature to find what the arguments for the method are and then the C variadic function macros to retrieve each of them in turn and add them to an NSInvocation object. This is then passed to -forwardInvocation:, and Objective-C programmers can pretend that they are using a Smalltalk-like language with stack introspection and that none of this is ugly code exists.

As you can imagine, this is very slow. For every argument, the forwarding function needs to look up the type and then copy the argument into the NSInvocation object.

OS X 10.5 introduced a couple of methods for making this a bit faster. These are called by the lookup function just before it calls the forwarding function, and gives the class an opportunity to install new methods in the class's method list. These are nice if you want to lazily create methods, but don't help much with proxies.

The most common use for proxies is to simply forward messages from one object to another. The method is not modified, it is just passed from one object to another.

10.6 added a new hook to the runtime that makes this trivial. The -forwardingProxyForSelector: method is now called before jumping to the forwarding function. This allows the object being sent a message to alter the message receiver. The return value for this method is an object, and the runtime will redirect the message to this receiver.

The content accessing proxies that I mentioned earlier are an obvious use-case for this. They send a message to the object that they wrap when they are created, and another one when they are destroyed, but simply forward every message that they are sent to the object that they wrap.

The implementation of this proxy is trivial. The forwarding is implemented by a method like this:

- (id)forwardingProxyForSelector: (SEL)aSelector
    return obj;

This is, of course, slightly slower than a direct message send, but the difference is not nearly as pronounced as if you go via the forwarding mechanism.

The nice thing about this method is that it doesn't add anything in terms of expressiveness. You can implement exactly the same forwarding behavior using -methodSignatureForSelector: and -forwardInvocation:; it will just be (a lot) slower. This means that you can add this method to your proxy classes without worrying about backwards compatibility. As long as you also implement the more traditional forwarding mechanism, your code will work on older versions of OS X (and GNUstep), but when it runs on 10.6 it will be a lot faster.

Proxy objects are not the only things that benefit from this. Pretty much any OS X GUI includes some subclasses of NSControl. Every button, for instance, is an NSButton instance, which is a subclass of NSControl.

The NSControl class is a simple NSView subclass that delegates all of its drawing and event handling to an NSCell. If you read the documentation of NSButton and compare it to NSButtonCell, you will notice a striking similarity. Almost all the methods declared on NSButton are really stubs that just forward to the cell. These are things like:

- (BOOL)isEnabled
    return [button isEnabled];

There are several hundred methods like this in the various NSControl subclasses. You can replace all of them with a single method in NSControl:

- (id)forwardingProxyForSelector: (SEL)aSelector
    return _cell;

This simplifies development, and may even make things faster. These methods are not speed-critical, so the small overhead from going via the forwarding mechanism is not very large. However, the extra instruction cache you free up for the rest of your code to use by replacing a few hundred methods with one can give a nice speed boost to the bits of your code that are.

NSControl isn't the only place where this is important. Cocoa inherits from OpenStep a number of patterns that were later codified by the Gang of Four. Cocoa programmers, therefore, tend to favor composition and delegation over inheritance.

With the new forwarding mechanism, you can now trivially implement everything that inheritance provides without actually using inheritance. This includes multiple inheritance.

Inheritance, in theoretical terms, is a special case of delegation. If an object doesn't implement a given method, then inheritance means that it implicitly delegates its implementation to its superclass. With a language like C++ or Lisp with CLOS, it can delegate the implementation to one of several superclasses.

If you look at how C++ implements multiple inheritance, you see that each object is just a structure containing all of the fields declared by each of its superclasses. When you cast a pointer in C++, you are really doing some quite complex pointer arithmetic. You can implement something equivalent in Objective-C now by creating instance variables for each of the “superclasses” that your class has, and attempting to delegate to each in turn using the forwarding mechanism, like this:

- (id)forwardingProxyForSelector: (SEL)aSelector
    if ([super1 respondsToSelector: aSelector])
        return super1;
    if ([super2 respondsToSelector: aSelector])
        return super2;
    return super3;

The lookup will first see if this class implements the method, then look at each of the superclasses. If none of these implement a method for the selector, then it will call this forwarding function. This will first check if super1 implements the method and, if so, forward it the method. If not, then it will try super2 and finally super3. If this doesn't implement the method, then the older forwarding methods will be called.

You can speed this up a bit by using the runtime functions instead of -respondsToSelector:. Because composition is now very easy to implement and almost as fast as inheritance, it becomes a better choice in a lot of cases.

You can also use this to speed up some less obvious things. The first place I used this new forwarding mechanism was to accelerate Quentin Math[ae]e's -ifResponds higher-order message proxy. This adds a category on NSObject that returns a proxy when you send it an -ifResponds message. The proxy then forwards message that the receiver responds to and silently ignores other. You can use this when sending delegate messages, like this:

[[delegate ifResponds] doSomething];

The proxy returned by this method now uses the new forwarding mechanism when the receiver does respond to the specified selector, so using this path is now quite fast, and is a lot cleaner to write than putting lots of conditionals in the code.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020