Re: EOSharedEditingContext Useful for Read-Mostly?
Re: EOSharedEditingContext Useful for Read-Mostly?
- Subject: Re: EOSharedEditingContext Useful for Read-Mostly?
- From: Marek Wawrzyczny <email@hidden>
- Date: Tue, 27 Jul 2004 17:10:52 +1000
On 27/07/2004, at 13:45, Art Isbell wrote:
On Jul 26, 2004, at 2:22 PM, Marek Wawrzyczny wrote:
your own editing contexts, whether they are session, shared peer or
nested ECs all are "children" of the Db EC.
Not sure what you mean by "Db EC" (database editing context?). All
EOEditingContexts are children of an EOObjectStoreCoordinator which
has one or more EOCooperatingObjectStores (usually EODatabaseContexts)
which are mapped to EOModels.
Yeah... Sorry I've fallen victim to the use acronyms bug.
Each time you make changes to an EO, change notification messages are
sent up to the DB EC and then down to all the children.
There are many notifications posted and received by EOF objects.
EOEditingContext broadcasts an
ObjectsChangedInEditingContextNotification when changes to an EO are
made. I believe this notification is intended for objects responsible
for displaying EO values in a UI. Other notifications are broadcast
when an EO is saved to its parent object store. These notifications
are eventually received by all other editing contexts so they can
update the same EO if it's present in these other editing contexts.
What's happening under EOF's covers is very complex and clever.
And just to clarify, all this happens within that instance only.
Marek Wawrzyczny
software engineer
-------------------------->
ish group pty ltd
http://www.ish.com.au
7 Darghan St Glebe 2037 Australia
phone +61 2 9660 1400 fax +61 2 9660 7400
_______________________________________________
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.