Re: EOSharedEditingContext
Re: EOSharedEditingContext
- Subject: Re: EOSharedEditingContext
- From: Anjo Krank <email@hidden>
- Date: Fri, 21 Dec 2007 08:26:42 +0100
Oh, and one should note that the SEC (in particular using the default
SEC) is a broken concept in the first place.
Lots of code out there uses sth like
public static EOEnterpriseObject OFF = ... get this from the SEC on
load
and later
if (state() == OFF) ... (or equals, doesn't matter)
which might fail horribly when you have more than one stack.
As a sidenote, the SEC adresses two wildly different issues:
- you have only one actual EO instance over a set of ECs (which saves
mem, from what I see, a larger EO takes about 1K without the actual
snapshot items)
- you cache the items on load and only ever refetch when they
invalidate (which saves fetches)
You can do the latter with normal ECs with a little thought (and using
Wonder helps a lot here), but not the first. At least not in a way
that doesn't take this 1k/object. Still, as the objects in an SEC
can't have outgoing relationships to non-SEC objects, you are limited
to lookup objects only which tend to be rather few, so this is most
likely not an issue.
Cheers, Anjo
Am 21.12.2007 um 08:10 schrieb Art Isbell:
On Dec 20, 2007, at 8:39 PM, Jonathan Miller wrote:
But given the scenario where you have a lot of objects that are
going to be read only e.g. the front end of a web site, what is the
best strategy?
I'm continuing to use shared editing contexts with no problems but
I've always paid careful attention to details of their proper use (<http://developer.apple.com/documentation/LegacyTechnologies/WebObjects/WebObjects_4.5/System/Documentation/Developer/WebObjects/DeltaDoc/EOF.html#CBGCHAIA
>). However, the apps that use shared editing contexts aren't high
traffic apps, so maybe I've been lucky. There have been EOF bugs in
the past that made using a shared editing context without problems
tricky, but I think these have been fixed. But don't play fast and
loose with shared editing contexts.
Aloha,
Art
_______________________________________________
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
_______________________________________________
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