Write-through proxy: easy slave-server de-synchronization

Hello all,

I've examined write-through proxy feature and
found that the state of Slave server could be easily
de-synchronized (against the repo state of Master-server).

I've figure out that if someone commits to Master while
there is no connection between Slave and Master (ISP failure?),
then sample post-commit hook fails to synchronize repo state.
And after such event, all subsequent attempts will fail because
incremental "dump load" will fail also (or Slave will just loose one
revision?)

Do I have right understanding of described things?
If so, users must be warned about usage of sample post-commit hook
in real life environments with such distributed configuration.

Of cause, I'm going to develop home-brew shell script,
which lacks certain drawback, but I'd prefer to have
Master->Slave synchronization built-in in SVN binary or
implemented as standalone synchronization server ;-)

Thanks,
Serge.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-15 17:39:58 CEST