On Sat, Jul 12, 2008 at 3:21 AM, Les Mikesell <lesmikesell_at_gmail.com> wrote:
> Reedick, Andrew wrote:
>
>> As for the Webserver farm example, it's "bogus." Using timestamps to
>> detect changed files isn't reliable (especially when you consider clock
>> skew.) Checksums are a better idea. Use 'svn info' to get the md5 of
>> the files that comprise the baseline. Compare the svn checksums against
>> the production file checksums. Only deploy files with mismatched
>> checksums. Problem solved without the use of unreliable timestamps or
>> commit-times.
>
> I don't get it... You want to check out another copy of content to add a new
> server to a farm. How is this approach going to mesh with the
> 'get-if-newer' requests coming in browsers that have already cached a copy
> from an existing server - or that will subsequently hit other servers after
> loading this copy?
AH! But that use-case is just as easily solved by using
use-commit-times! Because then too, on both servers, the timestamps
will be equal. So no new Subversion functionality is required to
address this problem.
Bye,
Erik.
---------------------------------------------------------------------
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-12 07:45:23 CEST