[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Methods, Inheritance, Exceptions, etc. (was: Re: Methods in SMIng ?)
- To: sming@ops.ietf.org
- Subject: Re: Methods, Inheritance, Exceptions, etc. (was: Re: Methods in SMIng ?)
- From: "Joel M. Halpern" <joel@longsys.com>
- Date: Wed, 02 May 2001 13:25:34 -0400
- Delivery-date: Wed, 02 May 2001 10:26:38 -0700
- Envelope-to: sming-data@psg.com
I believe that the relevant counter-argument is that people are already
doing those ugly things by hand, without the clarity that comes from
explicit method descriptions. Continuing to use a kludge because that is
what people have done does not seem a good answer when we can do
significantly better.
Yours,
Joel M. Halpern
At 10:42 AM 5/2/01 +0200, Juergen Schoenwaelder wrote:
>My argument for
>postponing methods is based on the observation that SNMP as well as
>COPS currently do not support method invocation natively and so you
>either have a feature in the data definition language which you can't
>use in practice (at least with SNMP and COPS-PR) or you have to do
>really ugly things to emulate generic method calls on top of what SNMP
>and COPS provides you.
- Prev by Date:
Methods, Inheritance, Exceptions, etc. (was: Re: Methods in SMIng ?)
- Next by Date:
RE: Methods, Inheritance, Exceptions, etc. (was: Re: Methods in SMIng ?)
- Prev by thread:
Methods, Inheritance, Exceptions, etc. (was: Re: Methods in SMIng ?)
- Next by thread:
RE: Methods, Inheritance, Exceptions, etc. (was: Re: Methods in SMIng ?)
- Index(es):