On 24 February 2011 06:35, sujata patra <[email protected]> wrote: > If I use cache , is it a concern?
No. > The time handler is processing a request > and expiry of cahe can free the data at the same time . right ? No. The check on whether the cache is valid is done once, *before* calling the iterator hooks, and then the handler itself. If the cache timeout hasn't expired (even by a nanosecond), then this check will pass, and the cache won't be reloaded. The iterator hooks and the handler will not subsequently check the cache timeout - they assume this has already been done. So the cache contents will remain valid for the processing of that request - even if the expiry timeout has since elapsed. But the *next* incoming request (possibly part of the same "snmpwalk" command) _will_ trigger the cache timeout and reload. Dave ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
