<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div>IMO point 2 can be neglected. It's an edge case, if you ask me.</div><div><br></div><div>The first point is no big deal. Verbosity or not. It's always better to strive for </div><div>a simple, easy to grasp solution. I believe (as a consumer of that API) that it should reflect the effective runtime model, no matter what. Including the defaults. Going through additional hoops & loops to figure out the effective runtime configuration is counter productive (curl,bash, etc) and will not be used.</div><div><br></div><div>Further more, consumer do not care if the attribute derives from a default value or not.</div><div>And why should they? </div><div><br></div><div>The fact that it's written back to xml, is an implementation detail to me. </div><div>But it should not mandate how the actually API works.</div><div><br></div>Ike<div><br><div><div>On Jul 29, 2011, at 2:31 AM, Brian Stansberry wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">1) The in-memory model no longer represents the user configuration<span class="Apple-converted-space"> </span><br>values; it also stores defaults. This is an issue when marshalling back<span class="Apple-converted-space"> </span><br>to xml; you either have to make the xml verbose by writing back all the<span class="Apple-converted-space"> </span><br>defaults, or you don't write back defaults and lose the fact the user<span class="Apple-converted-space"> </span><br>included the value in the original.<br><br>2) Possible versioning issues in a domain where different hosts run<span class="Apple-converted-space"> </span><br>different versions; i.e. if the version on the domain controller host<span class="Apple-converted-space"> </span><br>stores and pushes to servers a default value that a server running an<span class="Apple-converted-space"> </span><br>earlier version doesn't understand. This would really be a bug, since a<span class="Apple-converted-space"> </span><br>change in a default value should spur an increment in the subsystem's<span class="Apple-converted-space"> </span><br>schema and appropriate handling by the parser. But still, storing<span class="Apple-converted-space"> </span><br>defaults increases the chances of this kind of bug cropping up.</span></blockquote></div><br></div></body></html>