[SNMP4J] Basic Question about implementing SNMP Tables

[inliner683 at gmx.de]

>As I wrote in my previous email, INDEX column *must*
>be not-accessible in SMIv2.

Yes, that is clear now. But I am dealing with an existing
MIB where the modification is not allowed.

>SNMP4J does it not check such a correlation, since
>it is an exception case (and not allowed for "new"
>MIBs) 

Is is not allowed to create a "new" MIB in SMIv1?
Should it not be a design decision which version to 
use (of course ignoring all benefits from SMIv2 when
using SMIv1)?

>and since it can be easily implemented by the
>instrumentation.

That's true. Nevertheless the process I initially expected 
for creating a row was:

1) setting all index columns with appropriate values
2) setting all other columns with desired values
3) creating a row with the column information altogether
4) automatically getting rows with appropriate OIDs (with no requirement to set the OID anymore, since
   OID is known from index columns)

In SMIv2 the only difference is that the index columns are not accessible via e.g. a MIB browser, but the
value of the index columns must be defined as well (currently implicitly done via the OID parameter in 
createRow()-method).

It was just an idea (which perhaps would not have raised such confusion to me but would maybe would have
other disadvantages), the current API as is can be used well with the knowledge provided here.

Thank you.







-- 
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger