On 4 March 2010 04:22, Prasanna Varadharajan <[email protected]> wrote:
> So in createAndWait approach first the user has to enter the rowStatus object
> with
> value 5(for createAndWait) and followed by rest of the row creation objects,
Not quite.
When creating a row using 'createAndWait', the RowStatus assignment *must*
be included within the first SET request. But this can either appear
on its own,
or together with any (or even all) of the other column values for this row.
Then, once the row is complete, you'd use another SET request on the RowStatus
to make it active.
But the other column values can be assigned at any time during this process -
either as part of the initial 'createAndWait' request, or as separate
SET requests
in between, or as part of the final 'active' assignment.
> Because if the user sets the table objects first and then set the rowStatus
> with 4 or 5 means then there is no difference between createAndWait and
> createAndGo approach.
But you can't set the other column objects first when using 'createAndGo'.
Because there isn't a row to assign them into. The whole point of
'createAndXxx' is that this is what creates the row structure - ready
for filling
in the column values. You can't assign those column values unless you've
got a blank row to put them in.
Essentially 'createAndGo' is taking the ('createAndWait', column values,
'active') sequence, and compressing this into one SET request.
Dave
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
