• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
NSProtocolChecker vs. setProtocolForProxy:
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSProtocolChecker vs. setProtocolForProxy:


  • Subject: NSProtocolChecker vs. setProtocolForProxy:
  • From: Gwynne <email@hidden>
  • Date: Sun, 10 Oct 2004 13:48:46 -0400

I'm writing an application that makes significant use of DO for interthread communication. I'm quite appalled that both the only two relevant samples I could find for this were written, and I quote, "for a pre-Developer release of Rhapsody (ie OpenStep/Mach 4.2 for Intel + Yellow 1H)." But that's another issue. My question is this: When vending an object whose protocol I'm aware of, is it better to use setProtocolForProxy: on the "client" side, or to vend an NSProtocolChecker on the "server" side? Or both? Which one saves more interthread messaging? What are the advantages and disadvantages of each?

-- Gwynne, key to the Code that runs us all
Email: email@hidden
Web: http://musicimage.plasticchicken.com/

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
  • Prev by Date: Emailing RTF
  • Next by Date: RE: NSImageView PICTRepresentation
  • Previous by thread: Re: Emailing RTF
  • Next by thread: RE: NSImageView PICTRepresentation
  • Index(es):
    • Date
    • Thread