Re: CoreData multithreading question: @synchronized
Re: CoreData multithreading question: @synchronized
- Subject: Re: CoreData multithreading question: @synchronized
- From: Shawn Erickson <email@hidden>
- Date: Wed, 04 Apr 2007 10:42:01 -0700
On Apr 4, 2007, at 10:28 AM, Ruotger Skupin wrote:
Hi,
a short CoreData question. according to the manual:
Managed objects themselves are not thread safe. In order to work
with a managed object across different threads, you should lock its
context (see NSLocking).
Does that mean I can do a
@synchronized(myManagedObjectContext)
{
// .. do stuff
}
or do I have to do a:
[myManagedObjectContext lock];
{
// .. do stuff
}
[myManagedObjectContext unlock];
The later otherwise you are likely not using the same locking construct.
In general I believe the recommend practice is to not attempt to
modify a given managed object instance across threads but instead use
a managed object context per thread and only modify the objects you
get from the context on that given thread.
-Shawn
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden