Hi there,
On 17/02/2006, at 3:54 AM, Chuck Hill wrote:
From a posting not too long ago:
Although an EOSharedEditingContext sounds and appears like an
editing context, it's probably a more useful view to consider it a
very special EOObjectStore. I prefer to call it a "read mostly
object s
Dears,
Your help was great ! So I have to :
- create one ordinary
editing context per concurrent
reader in my application. I may let application deal or not with caching
- create one CooperatingEditingContext
per contributor.
Many thank's for your help,
Jérémy
Chuck Hill <[EMAIL PROTECTED]> a
Hi Jeremy,
On Feb 16, 2006, at 10:34 AM, [EMAIL PROTECTED] wrote:
Hi Chuck,
"> Keep in mind that while there is a separate EO object in each EC,
> that the _data_ is stored only _once_ in the snapshot. The EO just"
Do you mean that if 3 users fetch the same enterprise object
without chang
From a posting not too long ago:
Although an EOSharedEditingContext sounds and appears like an
editing context, it's probably a more useful view to consider it a
very special EOObjectStore. I prefer to call it a "read mostly
object store".
Several differences.
First, correctly locking a
Hi,
On Feb 16, 2006, at 7:32 AM, Arturo Perez wrote:
[EMAIL PROTECTED] wrote:
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
Tha
On Feb 16, 2006, at 7:15 AM, [EMAIL PROTECTED] wrote:
Hi,
After (re)reading the (famous) "Practical WebObjects" book
Infamous? :-P
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 :
[EMAIL PROTECTED] wrote:
Arturo Perez <[EMAIL PROTECTED]> a écrit sur 16/02/2006 16:32:23 :
> [EMAIL PROTECTED] wrote:
> >
> >
> > 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 ? DefaultShareEditingConte
Arturo Perez <[EMAIL PROTECTED]> a écrit sur
16/02/2006 16:32:23 :
> [EMAIL PROTECTED] wrote:
> >
> >
> > 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 ?
> >
>
[EMAIL PROTECTED] wrote:
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
That's what the DefaultSharedEditingContext is for (many re
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 data
10 matches
Mail list logo
