AW: [RFC] Server Dictated Configuration

Hi, Johan,

Von: Johan Corveleyn [mailto:jcorvel_at_gmail.com]

> Perhaps this issue can be deferred if the API would allow you to get / cache all the inheritable props, up to the repository root (since they are always readable anyway, regardless of authz). Not only "up to the nearest path-wise ancestor that has the property", but "give me everything up to the root". Then the concrete consumer of the prop can always add special syntax and corresponding inheritance / override / append behavior specific to its uses (a special syntax that defines how the multiple inherited props are to be "overlayed").

What about "svn:i:propname" defines inheritable properties, and "svn:o:propname" defines overlayable properties. The first one just goes to the nearest path-wise ancestor, while the latter one reads all of the properties up to the root.

And then let the property-consumers define a syntax or whatever to resolve the overlays for their specific use case.

Best regards

Markus Schaber

-- 
___________________________
We software Automation.
3S-Smart Software Solutions GmbH
Markus Schaber | Developer
Memminger Str. 151 | 87439 Kempten | Germany | Tel. +49-831-54031-0 | Fax +49-831-54031-50
Email: m.schaber@3s-software.com | Web: http://www.3s-software.com 
CoDeSys internet forum: http://forum.3s-software.com
Download CoDeSys sample projects: http://www.3s-software.com/index.shtml?sample_projects
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915