Re: editing context locking
Re: editing context locking
- Subject: Re: editing context locking
- From: Chris Hanson <email@hidden>
- Date: Wed, 6 Apr 2005 20:33:02 -0700
On Apr 6, 2005, at 2:15 PM, Florijan Stamenkovic wrote:
I was just wondering was it in this case necessary... Because it is
impossible for any other concurrent user to try to fetch, insert,
update or whatever on those objects, as they are still not
"officially" there. And that is what locking is supposed to prevent in
the first place, right???
Locking really is a rule, not a guideline. You can't second-guess it.
As Ben Trumbull said a few months ago:
All operations are "dangerous". Just because an operation *looks* like
it should not cause multithreading problems to you doesn't make it
safe in reality.
and
Locking is as much about transactional integrity as it is about thread
safety. It tells WebObjects "this resource is in use by this thread"
and the framework responds appropriately.
Full message:
<http://lists.apple.com/archives/webobjects-dev/2004//Dec/
msg00255.html>
-- Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden