Re: Local ECs (was Re: Can't modify EO objects! ARGH! =()
Re: Local ECs (was Re: Can't modify EO objects! ARGH! =()
- Subject: Re: Local ECs (was Re: Can't modify EO objects! ARGH! =()
- From: Ricardo Strausz <email@hidden>
- Date: Wed, 23 Jul 2003 17:48:05 -0500
OOOHHH!!!
this clarifies a lot of my confusion...
Gracias Art!!
On miircoles, juli 23, 2003, at 02:47 America/Mexico_City, Art Isbell
wrote:
The documentation is explicit about the need to lock your editing
contexts. We all want things to get better and easier. Certainly
this area of locking leaves a lot to be desired.
Maybe its the documentation (e.g.,
http://developer.apple.com/documentation/WebObjects/WhatsNew/WhatsNew/
chapter_1_section_7.html#//apple_ref/doc/uid/TP30000024/CHDEAHGF) that
needs to be clarified. I now realize that I was confused by
"Enterprise Object" vs. "EOEnterpriseObject", the first apparently
referring to an instance of any EOF class (e.g., EOEditingContext) and
the second, to an instance of a custom Enterprise Object class (e.g.,
an EOGenericRecord subclass). As in
"To ensure safe concurrent access to Enterprise Objects, it is your
fundamental responsibility is to lock the Enterprise Objects you use
directly."
I assumed incorrectly that this statement (italicized in the docs for
emphasis) was referring to EOEnterpriseObjects in an explicitly
multithreaded app. I think that many would interpret "Enterprise
Objects" as I originally did.
Dino
http://homepage.mac.com/strausz
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.