My immediate reaction to this discussion is that the model
is getting too complicated.
I'd be inclined to implement this as a single integer value,
with a range running from -1 to 1000
The description of the object would indicate the restriction
on acceptable values, and any attempt to SET a non-multiple
of 5 would fail with a 'wrongValue' error
As for the special-case of the mute value - that's probably most
easily handled by providing a dedicated client application, which
recognises the special value 'mute' and turns this into -1 internally.
My fear is that you're trying to squeeze too much automatic
processing into what is fundamentally a general-purpose (and
fairly low-level) tool.
Dave
------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
