Thanks,
Matt Upton
Juergen Schoenwaelder wrote:
> >>>>> Matthew Upton writes:
>
> Matthew> Does anyone know how to receive request Ids from an
> Matthew> asynchronous walk? I am only able to receive the request Id
> Matthew> from the first request in the walk. Here is an example:
>
> Matthew> set reqId [$s walk {ifType ifOperStatus} {myCallback "%E %R
> Matthew> {%V}"}]
>
> Matthew> This will return the first reqId for the walk, which matches
> Matthew> the one received by the first call to myCallback. However,
> Matthew> for all subsequent calls to myCallback the requestId field
> Matthew> (%V) has new result request Ids. Do you know if there is a
> Matthew> way to receive the subsequent request Id's (prior to
> Matthew> receiving them in the callback)?
>
> There is no way right now to receive all request IDs for an
> asynchronous walk. Adding this feature would actually turn the
> asynchronous walk into a synchronous walk since there is no way to
> know in advance how many requests are needed.
>
> Why are you interested in the request IDs at all?
>
> Juergen
> --
> Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw
> Technical University Braunschweig, Dept. Operating Systems & Computer Networks
> Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289)
--Matthew Upton Bridgewater Systems mupton@bridgewatersys.com
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.