Re: EO Object Lifespan / Editing Context
Re: EO Object Lifespan / Editing Context
- Subject: Re: EO Object Lifespan / Editing Context
- From: Art Isbell <email@hidden>
- Date: Wed, 16 Jul 2003 08:58:10 -1000
On Wednesday, July 16, 2003, at 02:17 AM, Pierre Bernard wrote:
There are other instances where passing the EO from one page to
another is more appropriate. E.g you go from a list to a detail page.
Here you would have to make sure that when you manipulate multiple EOs
all of them live in the same EC. Under WO versions prior to 5.2 you
also have to ensure that the lifetime of the EC is no shorter than the
livetime of the EOs you pass. To do this you can either pass the EC
from page to page or have it atteached elsewhere. E.g. the default EC
lioves as long as the session.
In most cases, the session's default editing context is sufficient, so
in these cases, you shouldn't have to worry about editing context life
span. However, there are some cases where the use of other editing
contexts is advantageous; e.g., an EOSharedEditingContext or
EOEditingContexts related to the sessions' default editing context as
parent-to-child (i.e., nested) or as peer-to-peer. EOF is very
flexible, but when learning WO and EOF, it's best to keep things as
simple as possible.
Aloha,
Art
_______________________________________________
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.