Questions about RequestList::receive

[Mike.Perler____radisys.com]

Frank,

It's not that I want to take an action on an invalid request. I need to 
report any errors to our system log (unfortunately, using a nonstandard 
API) when they occur, and a timeout is not actually an error. Currently, 
I'm reporting an error anytime that the RequestList::receive function 
returns a null pointer, but I've gotten complaints about that because of 
the timeout case.

If there is a way to call RequestList::receive with no time out, then that 
would also address my problem.

If I override the RequestList::receive function, then I have to recode all 
the logic of the base class function myself. I can't just call 
RequestList::receive from the derived class because I'll still run into 
the same problem. Therefore, I'm trying to use that as a last resort.

Mike





Frank.Fock at t-online.de (Frank Fock)
07/11/2001 06:46 PM

 
        To:     Mike.Perler____radisys.com
        cc:     agentpp-dl at agentpp.com
        Subject:        Re: Questions about RequestList::receive


Hello Michael,

I have no idea why you would like to take any actions
on invalid incoming requests? Can you give me an example?

Anyway, RequestList::receive does not provide such a
functionality. However, you may subclass RequestList by,
for example, MyRequestList and override RequestList::receive
there.

Hope this helps.

Best regards,
Frank

Mike.Perler____radisys.com wrote:

> Hello,
>
> If the RequestList::receive function has an error, it returns a null
> pointer. Is there any way to determine what the error was? I'd like to 
be
> able to differentiate between a timeout, an invalid community, and an
> actual error in the received SNMP packet.
>
> Also, is there a way to call RequestList::receive such that it won't 
time
> out?
>
> Thank you,
> Michael Perler
> Staff Software Engineer
> RadiSys Corporation