Databases Synchronization Proposal

  > Geert Jan de Groot <GeertJan.deGroot at ripe.net> writes:
  > 2. An update message is lost (forever).
  >    In this case, the secondary will never catch up. One can think of
  >    making some alarm bells that ring if the serial number difference
  >    between updates and the secondary gets over a certain threshold.
  >    In this scheme, this would be the only time that one would need to
  >    install a full newer copy of the database.
  >    Given the reliability of email, I think this will not happen 
  >    except under extreme circumstances. 

If you have the ftp-able files you can even automaticlly fix it at any
granularity you want. That is the idea behind them.

  > If things really get out of hand, then
  > one might think of using some reliable multicasting scheme, like
  > Van Jacobsen's WB has.

Now *that* is an idea!



-------- Logged at  Fri Mar 3 15:08:13 MET 1995  ---------