On 5/8/07, Andrea Smyth <[EMAIL PROTECTED]> wrote:
How useful is this? They reflect the state of the server at one point in time (i.e. service creation) - but that state may change over time. Unless of course you are assuming that the only interaction with a service that affects its functionality is via features, i.e. by adding/removing/toggling features. I can see how this may be a policy (in the sense of a coding style guide) in a customer scenario, but don't see how it can be enforced.
Thats a good point... On the other hand though I think it'd be handy to have a reference to the feature so at some point again to disable it as Seumas pointed out... - Dan -- Dan Diephouse Envoi Solutions http://envoisolutions.com | http://netzooid.com/blog
