On 2012-05-06 00:44, Philip Brown wrote:
it does seem to have potential overlap with windows registry types,
though. So while "sysproperties" could work with that, "svcproperties"
would not, seems to me.
If it makes sense to have this class shared between those two uses. I dunno.
Any ms-windows developers reading this?
Is there anything internally or externally valuable in conflating
svcproperties and registry entries?
Ask yourself the following questions:
* Do the different systems have the same parameters?
* Will it allow code-sharing? e.g. Do the two share a common
key-syntax which can be checked in the Type, while the provider
only manage read/write to the storage.
* Could Linux' sysctl code be integrated too?
* Can the Type provide a useful abstraction?
* Could the same abstraction be provided as a module wrapping the
low-level types?
I've ordered the questions somewhat. If any of them should be answered
no, it'd be an indication that separate types would be the way to go.
Best Regards, David
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
