Eric,
For what it is worth -- Luke is right. There are probably so many
variations on how developers would want such a cache managed, and the
fact that it couldn't be self-contained inside a single API object (or
for that matter, tier, as it would require server cooperation too),
that it probably would be wasted effort. Producing an implementation
would give rise to a hundred "I need this approach instead"
questions / criticism of the resulting API.
And again, Luke is right....for every problem, there is a developer
willing to be hired. :-)
Brad
On May 12, 2009, at 4:41 PM, Luke the Hiesterman wrote:
On May 12, 2009, at 4:38 PM, Eric E. Dolecki wrote:
I wish that Apple provided a convenient method for doing this as it
seems like something that could regularly be employed. I don't
think I'll go as far as using SQL, but thanks for all the tips!!
It doesn't really make sense for Apple to implement a caching
mechanism for your data. Every app has different data and different
caching needs. Caching is inherently a performance tuning activity,
and so each application will want to tune things to its own
situation. That's why God invented programmers.
Luke
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
