summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorelie <elie>2007-01-25 15:43:24 +0000
committerelie <elie>2007-01-25 15:43:24 +0000
commit64895c9905b25c188c78fe6b763c91d59b19daaa (patch)
tree3c8ef2c3af993228d1c59ba7f6e1f736efa41908
parentd0e73a99b82aa230c3d1d656751cf60a0edc9deb (diff)
downloadpysnmp-64895c9905b25c188c78fe6b763c91d59b19daaa.tar.gz
minor clarification on GETNEXT response table
-rw-r--r--docs/pysnmp-tutorial.html9
1 files changed, 6 insertions, 3 deletions
diff --git a/docs/pysnmp-tutorial.html b/docs/pysnmp-tutorial.html
index 16aa4f1..5fbe794 100644
--- a/docs/pysnmp-tutorial.html
+++ b/docs/pysnmp-tutorial.html
@@ -749,9 +749,12 @@ The <STRONG>varBindTable</STRONG> parameter is a tuple of
<STRONG>varBinds</STRONG> in <STRONG>varBindTable</STRONG> represent a
set of Managed Objects whose Object Names reside inside
<A HREF="#OID">OID</A> sub-tree of Managed Object name passed in request.
-In other words, call of <STRONG>nextCmd</STRONG> method for a single
-Managed Object might return a sequence of Managed Objects so that Object
-Name passed in request would be a prefix for Object Names returned in response.
+In other words, with this oneliner API, an invocation of
+<STRONG>nextCmd</STRONG> method for a single Managed Object might return
+a sequence of Managed Objects so that Object Name passed in request would
+be a prefix for Object Names returned in response (as a side note, the same
+method in Applications API would return <STRONG>varBinds</STRONG> as held
+in a single response, and regardless of the prefix property).
Properties of the <STRONG>varBinds</STRONG> parameter is the same as in
<STRONG>getCmd</STRONG> method.
</P>