Re: NSFileManager - thread safety issues?
Re: NSFileManager - thread safety issues?
- Subject: Re: NSFileManager - thread safety issues?
- From: j o a r <email@hidden>
- Date: Tue, 21 Mar 2006 17:57:34 +0100
On 21 mar 2006, at 17.37, Jim Correia wrote:
This sounds like incorrect and bad advice to me. For example, using
NSFileManager inside a @synchronized block doesn't guarantee that
all code that I didn't write (system or third party frameworks)
will do the same, so it hasn't magically added thread safety to
that class.
I guess we would have to assume that Apple makes a promise here,
namely that their frameworks doesn't use improper locking when
accessing such shared functionality. I'm not sure if that's a safe
bet though.
I agree that the issue with third party frameworks is a pickle. As
long as Apple doesn't provide class & object level locks with public
accessors, that's probably rather difficult to deal with. One way to
solve it would be to document when something like this is done in the
framework, so that you could add your own locks on these entry points.
I think that the documentations is a bit lacking here and have
already filed bug reports on that - please do the same if you agree!
j o a r
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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