Am 27.05.2008 um 22:58 schrieb Tonny Staunsbrink:
The reason consider using the same editing context, is that sooner
or later i properly wan't my eo's to be displayed to the user
At the end of the LongResponse I guess?
and usign two ec's will either force me to localize eo's (and using
global ids), which i consider a bit clumsy,
You either localize them or just fetch them into the new
EditingContext. Nothing clumsy about it.
or i will have to keep a reference to the newly created ec in the
background job, and that bookkeeping adds up, if the user can
perform several backend jobs.
The EditingContexts do the bookkeping anyway and saveChanges() will
propagate the changes.
If you are about to create new objects, I'd recommend using a new
EditingContext anyway, otherwise you might blow the whole Session if
something goes wrong.
Or did I miss your point?
atze
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
