Practical EditingContext Design Question
Practical EditingContext Design Question
- Subject: Practical EditingContext Design Question
- From: email@hidden
- Date: Thu, 16 Feb 2006 16:15:24 +0100
Hi,
After (re)reading the (famous) "Practical
WebObjects" book and paying attention to the CooperatingEditingContext,
I'd like to implement a better solution for our portal.
In a portal, there is two types of users
:
- the readers,
- the contributors
The readers read informations (from
the databases) displayed on pages
The contributors do the same AND they
create/modify/delete objects
Actually (before reading the book),
we use the session.defaultEditingContext for each user (session)
But it means that for each user we will
have a (local) copy of the enterprise objects fetched by the visitor. If
we have a lot of users (and that's the case) we need more and more memory...
But finally isn't it possible to :
- use only one editing context for all
the readers (except forl informations like authentifcation that will still
be in the defautEditingContext)
AND
- one CooperativeEditingContext (thank's
to Sacha and Charles) each time a contributor is making change. After each
contribution, we just need to populate the changes to the global one editing
context.
Is it a good solution ?
In the book, different king of EditingContext
are explained but wich one do we need to use for the readers ? DefaultShareEditingContext
? Other ?
Many thank's for any advice,
Jérémy _______________________________________________
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