RE: Multiple sets in one pdu

"Yong Chen (yongche)" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <52E903A38F544F46A2A6632AC66103EED7F506@xmb-sjc-221.amer.cisco.com>
Thanks a lot Dave. But in ChangeLog, it says:

Fixes:
    - the agent should properly handle requests in the right order.
      (e.g., restrict the agent to processing only one SET at a time) 

Seems it is opposite to what you said.

Also the ordering of varbinds in a SET request may have some
significance because of dependency between the varbinds. Where can I
find doc regarding the simultaneously processing SET assignments?

Thanks,
Yong Chen

-----Original Message-----
From: Dave Shield [mailto:[email protected]] 
Sent: Wednesday, October 19, 2005 1:08 AM
To: Yong Chen (yongche)
Cc: [email protected]
Subject: Re: Multiple sets in one pdu

On Tue, 2005-10-18 at 18:08 -0700, Yong Chen (yongche) wrote:
> I'm facing a problem with multiple sets in one pdu, basically it's 
> sequence issue.

Remember that SET assignments are processed "as if simultaneously".
You cannot rely on a particular ordering of varbinds in the SET request.
This should *NOT* affect the success or failure of the assignment.


> It seems the agent does some optimization....
> This is not what I want, I want the original sequence.

Tough.
You should *NOT* rely on any particular ordering of varbinds.
Your code should be robust enough to cope with the assignments being
provided in *any* order.

Dave


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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.