Re: Editing Context Choices
Re: Editing Context Choices
- Subject: Re: Editing Context Choices
- From: mmalcolm crawford <email@hidden>
- Date: Sun, 1 Aug 2004 21:49:02 -0700
On Aug 1, 2004, at 4:09 PM, Hunter Hillegas wrote:
I haven't seen a document that explained each type and maybe gave some
examples of best uses for each...
Please file an enhancement request (<http://bugreport.apple.com>). If
it is something that people find confusing, it's worth explaining.
For instance, if I have a bunch of data that is read-mostly and
accessed often, which editing context should I use? Shared and stored
in the Application? Session and looked up each time? What are the pros
and cons?
I wouldn't want to propose cast-iron rules, it's mainly based on
trade-offs.
Shared editing contexts are read-mostly, and more difficult to update.
You can only make "incoming" relationships from objects in other
editing contexts. But you only have one copy of every EO.
"Normal" editing contexts give you the full range of abilities, but
each EO you need access to must appear in each context, so for your
read-mostly common data you'll get duplicates.
mmalc
_______________________________________________
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.