On Mon, 2007-03-05 at 14:50 -0800, Karl Fogel wrote:
> Remember that it's okay to have multiple representations of the same
> historical data present at the same time -- readers don't care which
> source is behind the data they're getting...
[...]
> ...so upgrading the format can happen whenever you're ready to make
> new connections from older clients return errors.
You're still stuck thinking about the standard network server
architecture, with only one piece of back-end code on one machine
accessing the disk representation of a repository. That's the
recommended setup, but it's not the only one. In that setup, there's no
issue upgrading the format of a repository; it doesn't induce any
incompatibilities with the clients.
We're talking about the case where the disk representation of a
repository is being shared over a network filesystem to multiple
machines, each using potentially different back-end code to access the
repository. That's a more difficult case, and we can't use the network
layer abstraction barriers to pull the wool over anyone's eyes.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 6 00:04:08 2007