Re: Multiple EOObjectStoreCoordinators

Hi!

Where did you read that EOObjectStoreCoordinators were meant to 
communicate?

AFAI, having separate EOObjectStoreCoordinators produces EOF stacks as 
separate as having them running in separate applications. Only 
EOEditingContexts belonging to the same EOF stack keep sync. There is 
however a framework that's talked about regularly on this list that 
allows for change notification among different applications. The names 
escapes me, but I'm sure others will point you to it.

Then again, why is change notification so important to you? Wouldn't a 
good/agressive refreshing strategy do the job? E.g. in an application 
with a search-list-detail workflow you could create a fresh editing 
context each time you hit a search form. Create that editing context 
with a short fetch timestamp lag and you'll always be seeing fresh data.

Pierre.

On Thursday, February 6, 2003, at 09:14 PM, 
<[email protected]> wrote:

> I have this problem:
>
> I create an EOObjectStoreCoordinator per session.
> Then, I create an editingcontext associated to the 
> objectstorecoordinator that i created before.
>
> The problem is that when in a session I change an eo object, the other 
> session never gets a notification of the change, and so it has 
> different data. Webobjects documentation says that 
> EOObjectStoreCoordinators mantain persistence between them, but I dont 
> see it. i'm i missing something here? how can i make 
> objectstorecoordinators notify updates between them?????
>
> thanks
> __________________________________________________
>
> Todavía no tenés tu Ciudad Internet Mail? Obtenelo ahora! - 
> http://webmail.ciudad.com.ar
>
> Descargá Gratis el nuevo Internet Explorer 6.0, el mejor software para 
> actualizar tu PC.
> http://www.ciudad.com.ar/ar/servicios/ie/
>
> _______________________________________________
> EOF mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/eof
>