Re: [RFC] Server Dictated Configuration
From: Thomas ┼kesson <thomas_at_akesson.cc>
Date: Sat, 28 Jan 2012 13:01:31 +0100
First of all, thanks for working on server dictated config and inherited properties. We use Subversion as the core of a Document CMS (with focus on structured XML authoring). Some of the components we develop are available as open-source: http://repossearch.com/
We would be absolutely thrilled to see inherited properties implemented! There are many potential use cases for us, configuration of our services being one of the most imminent. Our primary input to this thread is that we would very much like inherited properties to be a generic feature accessible to other uses than core Subversion, preferably with API-support.
On 28 jan 2012, at 10:30, Ivan Zhakov wrote:
While following the thread, I have debated this with myself over the last few days and each approach has advantages.
Consumer inheritance (the property consumer decides which are inheritable)
Defined inheritance (the server decides)
I am fine with either way, but I am swaying towards "defined inheritance" mainly because of the last item, "better APIs". Both the WC and the server could make it much simpler for the consumer to read and set inherited properties. Specifically, the server is in a much better position to efficiently (fewer round-trips) respond to proplist AND provide a single proplist containing both regular and inherited properties.
This is an archived mail posted to the Subversion Dev mailing list.