On Apr 21, 2011, at 3:23 PM, Brian Stansberry wrote:
> to further distinguish these two I would suggest the following,
> which may apply to other subsystems as well:
>
> - if changing the configuration impacts the runtime state (i.e.
enabled->disabled)
> then make it an operation
> - if it's merely configuration then make it an attribute
>
I'm fine with this, but let's clarify what "impacts the runtime state"
means. Many configuration changes will impact the runtime state. Instead of "impacts
the runtime state" I'd say "results in an MSC service starting or
stopping." That's the main case where an action has rippling effects the user
might not anticipate
+1