Re: Configuration Indirect Synchonisation
From: Lothar Geyer (Lothar.Geyer_at_EDV-Berater-Online.de)
Date: 02/27/04
- Next message: kniva: "Re: Configuration Indirect Synchonisation"
- Previous message: kniva: "Re: Configuration Indirect Synchonisation"
- In reply to: kniva: "Re: Configuration Indirect Synchonisation"
- Next in thread: kniva: "Re: Configuration Indirect Synchonisation"
- Reply: kniva: "Re: Configuration Indirect Synchonisation"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 27 Feb 2004 10:40:41 +0100
Hi Kniva,
kniva wrote:
> .sgn file only holds the name of the jet synchronizer,no other data.in
> indirect sync the synchronizer must see only the replica it manages,not
> the remote one.
so, what happens during synchronisation? When the replica is not on the
LAN, the synchronizer only sees the local replica. Then - when connected
- something is written to the dropdown folder. Some time later the
"central" synchronizer finds this "something" and synchonizes with the
"central" replica.
But it seems, I am wrong. Could you explain, please?
> in your scenario coping and moving the replica will corrupt your data.
even when I use the replication manager function "copy replica"?
> you can determine which rows are to be transfered in synchronization by
> cheking the generation counter(the s_Generation field).those with the
> highest values are the updated ones.
so I can write my own synchronizer? Well, I do not really plan to do so ;-)
Lothar Geyer
- Next message: kniva: "Re: Configuration Indirect Synchonisation"
- Previous message: kniva: "Re: Configuration Indirect Synchonisation"
- In reply to: kniva: "Re: Configuration Indirect Synchonisation"
- Next in thread: kniva: "Re: Configuration Indirect Synchonisation"
- Reply: kniva: "Re: Configuration Indirect Synchonisation"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|