Hi,
During a SET operation the custom handler will be called 4 times, 2 with old
values and 2 with new ones (Reserve1, Reserve2, Action, Commit). If the same
handler is used also for GET operations (HANDLER_CAN_RWRITE) will be called
once only (let's call it Reserve1). How can one distinguish between GET and SET
calls? Or even better can anyone tell apart the different stages alltogether
from another within the custom handler?
This is mostly for efficiency reasons. I could read the table from the
application in all stages before action, but if the table has a lot of data it
creates a lot of unnecessary I/O and delays. An example:
dotable -> Reserve1? -> Is it get or set? If get I need I/O and remain on
Reserve1. If set do nothing and advance to Reserve2.
dotable-> Reserve2? -> Is it new get Reserve1 or old set Reserve2? If get need
I/O and stay on Reserve1. If set do nothing and advance to Action.
Variables are identical in these cases and do not help in discriminating them.
TIA,
Nikos
------------------------------------------------------------------------------
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
