Help in SNMP SET done in multiple transactions

Nitin Naveen <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <OF908EB7E0.7B73C877-ON652573D1.001388BE-652573D1.00139091@hsc.com>
Hi,
 
I want to understand how to implement support for SNMP SET's that are 
related but come in multiple SNMP SET PDU (i.e. multiple transactions). I 
have two scalars that allow me to know when the multi transaction have 
started and when they end. My aim is to keep buffering the data in 
temporary buffer from the multiple SNMP SET PDU (transactions) and when 
the manager indicated end of update only then I update by actual tables. 
Kindly suggest.
 
Regards
Nitin




*****************************************************DISCLAIMER*****************************************************

This message and/or attachment(s) contained here are confidential, proprietary to HUGHES SYSTIQUE and its customers. 
Contents may be privileged or otherwise protected by law. The information is solely intended for the entity it is 
addressed to. If you are not the intended recipient of this message, it is strictly prohibited to read, forward, 
print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, 
please notify the sender immediately and delete the message.

********************************************************************************************************************

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.