Re: Synchronizing data displayed by two instances of my app
Re: Synchronizing data displayed by two instances of my app
- Subject: Re: Synchronizing data displayed by two instances of my app
- From: Denis Stanton <email@hidden>
- Date: Sat, 3 Apr 2004 08:24:28 +1200
On 02/04/2004, at 8:15 PM, Sam Hart wrote:
You need Change Notification, it is the best way to maintain coherency.
While I am here, do not set the default timelag to too small a number.
Thank you Sam.
I see that some advice on the timelag used smallish number, like "2",
as if that meant 2 seconds, but the documentation states that the times
are in milliseconds so I'll try something more realistic.
I'm not sure that the lag setting is going to help as Art's post
implies that the lag only applies on the creation of a new ec. I was
looking for something that would ensure that an update (ie, a fetch)
would get current data. It looks like the lag setting only promises
that a new session will get data that is current at the time the ec is
first used. Thereafter it will be up to an hour out of date. I'm
surprised that this isn't made easier. Surely I'm not the only one who
needs to be confident that the screen display indicates what is in the
database, not merely what WAS there an hour ago.
Denis
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.