Re: Methods in the NIM requirements

[Keith McCloghrie <kzm@cisco.com>]

>  ...  If I understand your
> comments below, you would describe attributes as any element that is
> persistent for the life of the object.

There are attributes which do not have values for the life of an object.
For example, interval counters do not have values between the birth of
an object and the expiry of an interval timer.  Similarly, it seems
reasonable that an attribute's value could have a TTL, and you should
be able to read it while it's still valid.

> Attributes can be read or written

or both.

> Methods deal with cross-object interactions.

If "clear an object's counters" were allowed, wouldn't it be a method,
but have no interaction with any other object ??

Keith.