|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]|
I see... but if I need to proactively remove an object from a cache in dealloc, this creates a very unfortunate dependency between the object and its cache... something I would like to avoid altogether :/ Any idea about how to implement a generic weak cache mechanism which doesn't depends on any help from the objects it's holding to stay valid?
What about a cache which retains its objects as usual, but periodically checks their retain counts and release them when there's only one reference left?
|>Re: WeakCache? (From: Marco Scheurer <email@hidden>)|
Visit the Apple Store online or at retail locations.
Copyright © 2011 Apple Inc. All rights reserved.