Should an NSLock instance be "global"?
Posted
by Alex Reynolds
on Stack Overflow
See other posts from Stack Overflow
or by Alex Reynolds
Published on 2009-10-17T16:21:30Z
Indexed on
2010/05/13
13:04 UTC
Read the original article
Hit count: 351
Should I make a single NSLock
instance in the application delegate, to be used by all classes? Or is it advisable to have each class instantiate its own NSLock
instance as needed?
Would the locking work in the second case, if I, for example, had access to a managed object context that is spread across two view controllers?
© Stack Overflow or respective owner