• 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
KVO and the observeValueForKeyPath bottleneck
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

KVO and the observeValueForKeyPath bottleneck


  • Subject: KVO and the observeValueForKeyPath bottleneck
  • From: Matt Neuburg <email@hidden>
  • Date: Fri, 14 Jul 2006 10:44:19 -0700
  • Thread-topic: KVO and the observeValueForKeyPath bottleneck

I'm just curious about how people are handling the fact that when you do
KVO, all your notifications are bottlenecked through a single method,
observeValueForKeyPath:... This is a very unpleasant and crude architecture
(in contrast to NSNotification where, when a notification comes in, it is
automatically routed to the selector of your choice). I really don't want a
series of "ifs" here. I can imagine a simple dispatcher architecture based
on NSSelectorFromString; is this the sort of thing people are using? Thx -
m.
--
matt neuburg, phd = email@hidden, <http://www.tidbits.com/matt/>
A fool + a tool + an autorelease pool = cool!
AppleScript: the Definitive Guide - Second Edition!
<http://www.amazon.com/gp/product/0596102119>



 _______________________________________________
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

  • Follow-Ups:
    • Re: KVO and the observeValueForKeyPath bottleneck
      • From: Jakob Olesen <email@hidden>
    • Re: KVO and the observeValueForKeyPath bottleneck
      • From: Aaron Burghardt <email@hidden>
    • Re: KVO and the observeValueForKeyPath bottleneck
      • From: George Orthwein <email@hidden>
  • Prev by Date: NSConnection/NSSocketPort per-subthread Mach port leak
  • Next by Date: peekaboo, icu
  • Previous by thread: NSConnection/NSSocketPort per-subthread Mach port leak
  • Next by thread: Re: KVO and the observeValueForKeyPath bottleneck
  • Index(es):
    • Date
    • Thread