<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><br></div><div>The CLI offers low level DMR operation, which offer a lot more possibilities</div><div>then the CLI's it's high level commands.</div><div><br></div><div>If compare the web interface and the CLI, compare the CLI high level commands to the</div><div>web interface. On this level they should remain synced as much as possible.</div><div><br></div><div>I am not objecting to implement any nitty gritty dada source configuration option,</div><div>but we need to get the priorities straight. Therefore I'd say let's focus on the frequently used</div><div>features for sysadmins and developers.</div><div><br></div><div>IMO it's fine with to point users to the the CLI for more fine grained configuration options.</div><div>("the good of the many outweighs the good of the few"). </div><div><br></div><div>Ike</div><br><div><div>On Jul 22, 2011, at 12:01 PM, Vimal Kansal 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; ">However, this may lead to an inconsistency of sorts, as using CLI when you execute :read-resource, you get to see all the configured properties, but when you use UI, you will see only a subset. I am not sure, how appropriate it would be to have this inconsistency.</span></blockquote></div><br></body></html>