mitzel@jerico.usc.edu (Danny Mitzel) (03/24/91)
does anyone have an example of how to handle the SNMP set operation under SMUX? i understand the principle of the two phase commit implemented but am unsure of how to efficiently handle this. #1. when a set request is first passed along to the specific client it identifies the (possibly multiple) instance(s) to be modified, and their values. then if all goes well the client later receives a commit request which includes no further info, is it up to the client to create and maintain a list of values to change between the time it sends the reply and receives the commit? #2. inserting a value in a reply PDU is easy for a get request because all you have to do is insert the values into the var-bindings portion of the already available structure. However when a client receives the commit SMUX PDU it is required to return a reply PDU but this time it doesn't already have the template to insert the values into. does the client have to create the entire reply PDU or just a var-binding structure? does the storage allocated for the original request PDU have to be released? are there any utility routines available to assist with this? if anyone has some code fragments showing an example handling sets that'd be great, but any advise is also greatly appreciated. thanks, danny (mitzel@usc.edu)