>>>>> On Fri, 25 Jun 2010 16:49:01 +0300, makkalot <[email protected]> said:
m> Yes i found the netsnmp_subtree_load but couldnt see the place where it stores m> the subtree into global list. Which data structure is that global "tree like m> ordered list" ? See the lookup_cache_context structure and the sub-structure "lookup_cache". The first holds the list of contexts things are registered under and the second holds the actual registered trees. m> Thanks for your answer it is clearer now. There is a tree like linked list m> that has the oids and every snmp_subtree has reginfo in it (that stores the m> handler chains). Therefore when a request comes its oid is searched in tree m> and the handlers that match in that snmp_subtree are called (in reverse order m> they were injected). Is it right ? That's pretty much it. There are extra complexities added in as well, mostly for optimization sake. (like we actually have an active list of the last 8 trees searched so that we can try and start quickly at the right place when another request comes in). -- Wes Hardaker Please mail all replies to [email protected] ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
