Pavlin Radoslavov wrote: > Ben Greear <[EMAIL PROTECTED]> wrote: > > >> It seems to me that these two have significant overlap in >> meaning and perhaps could be consolidated? >> >> Why do we have both of them? >> > > Conceptually they are populated using different mechanisms, but > pragmatically they should contain same information. > > The _live_config IfTree is populated/updated asynchronously by the > IfConfig Observer that tracks the kernel upcalls. > The _pulled_config is populated on demand (explicitly) by the > pull_config() method. > In other words, _live_config is a moving target, while > _pulled_config is a snapshot. > I merged these, and it seems to work fine. Eventually, that might be a good way to get rid of some many pull_config() calls as well. I can't think of any reason why we'd ever *want* pulled_config to get stale, so letting observer update it seems valid. Maybe I'm missing something?
Thanks, Ben > Regards, > Pavlin > -- Ben Greear <[EMAIL PROTECTED]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ Xorp-hackers mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
