Databases Synchronization Proposal

  > cengiz at ISI.EDU (Cengiz Alaettinoglu) writes:
  > 
  > I think having a master registry is a good idea. 

It is not only a good idea but a requirement!  You usually do not have
distributed notarys either. 

  > A record should not
  > be registered anywhere if it is not registered at the master
  > registery. 

Definitely.  If a registry receives an update for a "source:" it is not
master for it can either bounce it back or send it on to the correct
master with a notification back to the sender. 

  > I think master registry should issue both serial numbers
  > and time stamps. That is records of the sort:
  > 	database serial-number timestamp operation object	

That would really catch everything. 

The time stamp will reflect the time of the operation made at the master
registry.  This will enable everyone to build a database state at a
given point in time.  This might also be useful for the master itself
in case of emergencies!

The serial numbers can be used to discover missing updates in case of
unreliable transport methods like e-mail.  This can then cause a
re-fetch of the missing updates via another channel. 

  > These records can be stored for future ftp as diffs or sent around via
  > email (or both). 

Exactly. 

  > My 1000 Turkish Liras:-) which is only 2 cents:-(

My 5 dutch cents (no smaller coins available).  It is still slightly
more than 2 US$-cents but slowly getting there ;-). 

Daniel



-------- Logged at  Mon Mar 6 16:42:52 MET 1995  ---------