On Thu, Jan 5, 2012 at 4:17 PM, Konstantin Kolinko
>> The approach TortoiseSVN and some other clients take does work pretty
>> nicely but I also think they reveal the short comings in using
>> properties. For convenience, TortoiseSVN does not force you to set
>> these properties on every folder and instead will walk to the root of
>> your WC to find them, but then this also exposes the problem that if
>> you did not checkout the folder that has those properties you are back
>> to square one.
> As I wrote in this very thread two days ago , this shortcoming
> could be solved if the properties for the parent folders were present
> in the WC.
> Now that wc has a database it could store those properties.
I think the last time this feature (server-dictated configuration) was
proposed, this was the approach considered. Perhaps the new WC format
makes it more possible than last time, I do not know. It seems like
it would be less efficient though. The approach outlined in the
proposal, via its usage of the hash and comparing the hash when the
session is opened makes it easy for the client to know when settings
have changed. If we use properties in the manner described, then
doesn't every RA session have to inspect every folder all the way back
to the root on every request?
It seems like someone would have to come up with a way to solve this
problem, or remove the requirement of inheriting properties that are
not already in the WC.
Received on 2012-01-05 22:24:26 CET