[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Pre-Design Discussion of Server->client configuration

From: SteveKing <steveking_at_gmx.ch>
Date: 2005-04-29 20:00:45 CEST

John Peacock wrote:
> steveking wrote:
>> John Peacock wrote:
>>> Common config files could be stored in a hash by UUID in the
>>> .subversion directory for caching purposes, but it would mean that
>>> deleting a WC would not remove this information from the disk (unless
>>> a new 'svn release' command were added).
>> Is the '.subversion' directory you mention here the one where the also
>> the 'config' and 'server' file is located? (%APPDATA%\Subversion on
>> Windows)?
> Yes, sorry, I should have been more specific (or more general, depending
> on how you look at it). The one [possibly serious] drawback is that
> this data isn't "connected" to the WC in any way except internal to the
> client code, so deleting the WC files in the filesystem doesn't remove
> all data associated with that repository.

Why would that be a serious drawback? I mean the same applies to the
auth data cached right now, and I've never heard of a drawback (except
for that data not being encrypted, but that's another issue and
something which is taken care of in 1.2 on windows).
Can you provide maybe some examples why this would be a drawback?


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Apr 29 20:06:46 2005

This is an archived mail posted to the Subversion Dev mailing list.