Possible idea on repository-wide defaults

I've been thinking a little about how to go about handling repository-wide
defaults (mostly because of how they relate to the keywords patch). Would it be
appropriate to consider any repository-wide default like:

        keywords,
        .subversion/config stanzas
        autoprop
        global ignores
        etc.

as very much like properties of the repository itself? Consequently, the
existing property code could be used to retrieve this information from the
server, via an otherwise inaccessible path. Something like a path which the
user is not able to type in directly, but which the clientcode could construct.

Is this too hacky a solution? It would seem to be worthwhile pursuing this,
since it wouldn't be a problem for compatibility (an older client wouldn't ask
and a newer client vs an older repository could just fail gracefully if the path
didn't exist).

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org