Re: Practical EditingContext Design Question

[email protected]
Newsgroups gmane.comp.web.webobjects.devel
Message-ID <OF18F7BD41.804C3345-ONC1257117.0056CD3B-C1257117.0057B94B@hebergence.fr>
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 ?
> >
> > Many thank's for any advice,
> >
> > Jérémy
> That's what the DefaultSharedEditingContext is for (many readers, few 
> writers) but most people have trouble implementing it properly.  That 
may or
> may not be because it's buggy.
Ok, I will try. Just a question :
- "How do WebObjects populate the changes made in all the 
CooperativeEditingContext (used by the contributors) in the 
DefaultSharedEditingContext (used by the readers) ?"

> 
> What you can do instead is have an application-level editing context and 

> set your session's defaultEditingContext to that.  Then when a writer 
comes
> in you don't set it.
> 
> Of course, you'll have to make sure that you do multithreading and 
> locking properly in either case.
> 
> Alternatively, you can have one app for readers and another for 
> writers.  Depending on your requirements you may run into stale data 
issues.
Yes, but it hard to :
- maintain two differents applications using the same datas (even if it's 
just reading)
- sometimes the readers become contributors in the same session

> 
> -arturo
>

_______________________________________________
WebObjects-dev mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.