Hi Dave! Thank you for this overview. It really should be made a part of the documentation
> Another possibility is to use the 'magic' field of the 'cache' > parameter. This is also an opaque pointer, which is again made > available to the handler routine. Can you please tell me where this pointer is made available to the handler routine? While setting the pointer is easy to spot in the extend.c you mentioned I wasn't able to locate the access to the cache in a handler routine > Another possibility is to use a private data structure, shared > between the cache_load routine and the end handler. This is > perhaps not the cleanest approach from a coding purist's point > of view, but it's simple and it works. Well, it works at least as long as there are no multi threading issues (second thread updating the cache before the first one finished getting the data from the cache). Are such multi threading issues somehow prevented? Jörg ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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
