I agree with your suggestion for two objects (and with their names
and postulated semantics). In a number of standard (and proprietary)
MIBs, there is a 'highestActiveIndex' object. But anytime that the
rows are actually quite volatile, the wrap problem makes this object
- Ira McDonald (outside consultant at Xerox)
PS - I can't reach the PWG server in the last two-and-a-half days,
to retrieve your posting about the 'grand entente' between Tom
Hastings, Ron Bergman, and yourself. Is there something wrong at
the PWG server end? Could you mail to the two '.pdf' files to
'Joe_Filion@mc.xerox.com', so that Joe and I could look at them?
>--------------------- Included Message -----------------------------<
Received: from zombi (zombi.eso.mc.xerox.com) by snorkel.eso.mc.xerox.com (4.1/XeroxClient-1.1)
id AA08285; Wed, 9 Apr 97 20:25:03 EDT
Received: from by zombi (4.1/SMI-4.1)
id AB04599; Wed, 9 Apr 97 20:22:19 EDT
Received: from lists.underscore.com ([220.127.116.11]) by alpha.xerox.com with SMTP id <17957(13)>; Wed, 9 Apr 1997 16:24:44 PDT
Received: from localhost (daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) with SMTP id TAA05262 for <email@example.com>; Wed, 9 Apr 1997 19:19:52 -0400 (EDT)
Received: by pwg.org (bulk_mailer v1.5); Wed, 9 Apr 1997 19:19:01 -0400
Received: (from daemon@localhost) by lists.underscore.com (8.7.5/8.7.3) id TAA05158 for pmp-outgoing; Wed, 9 Apr 1997 19:18:43 -0400 (EDT)
From: Harry Lewis <firstname.lastname@example.org>
Subject: PMP> jmGeneralLeastActiveIndex
Date: Wed, 9 Apr 1997 16:21:17 PDT
Content-Type: text/plain; name="MEMO 04/09/97 19:19:24"
Epilogue: Harry Lewis - IBM Printing Systems
There was quite a bit of discussion upon adding this to the jmGeneral table
last week in Austin. After reviewing back here, we still don't see how this
value serves it's purpose. Does someone have a write-up of exactly what this
object is supposed to do?
We feel another object is also required... basically something like
jmGeneralHighestActiveIndex otherwise it is very difficult to avoid walking the
We feel that these should be named
this helps get around the wrap problem.
Using these two objects, an application should be about to determine where to
start in the table (Oldest) and where to stop (Newest) and should also know
there will be a wrap if Newest is a smaller number than oldest.
I don't think we felt we'd fully solved this problem in Austin. If we did, can
someone explain how it works?