Hi,
When a set request is received, my sub-agent completes this operation using
transactional semantics. If a set request had come for more than 1 attribute
for the same table, then this set would be done as part on one transaction.
Ex: For the following
./snmpset -v 2c -c clovis 1.3.6.1.4.1.94480.1.1.1.10.1.2.0 i 10
1.3.6.1.4.1.94480.1.1.1.10.1.3.0 i 10 , my implementation requires the set
on both attributes to be done as part of one transaction.
Now everything is fine when the set on attributes is done on the same table
as there is a handler generated/table. ( The code is generated using
mib2c.iterate.conf)
Now consider when a set is done on attributes belonging to different table
like the below
./snmpset -v 2c -c clovis 1.3.6.1.4.1.94480.1.1.1.10.1.2.0 i 10
1.3.6.1.4.1.94480.1.1.1.7.1.1.0 i 10
Like before, my sub-agent is expected to process the request as a single
transaction. The problem is there is a handler generated per table(say h1
and h2 for tables t1 and t2) and my sub-agent has no way of knowing whether
the set requests that come through h1 and h2 is part of the same bulk set
request.
What i want is some way to recognize that all these set requests for
different attributes are part of one single request, so that i can
accumulate the jobs and then start a single transaction to complete this
request.
Registering the same handle h1 for both tables t1 and t2 doesnt help as h1
is called twice now.
Any ideas?
--
Thank you,
Deepak B.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
