Re: Multiple EOObjectStoreCoordinators
james o <[email protected]>
| Newsgroups | gmane.comp.web.webobjects.eof |
|---|---|
| Message-ID | <[email protected]> |
On Thursday, February 6, 2003, at 03:25 PM, Pierre Bernard wrote:
> 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.
what is a "good/aggressive" refreshing strategy? i'm having
difficulties seeing EO's changed in other application instances.
invalidateAllObjects gives me fresh data but this doesn't seem like the
correct way to go about this.
thanks,
./james
{ http://primax.com : 513.772.1223 }