On Thu, 13 Jan 2005 10:52:16 +0000 Dave wrote: DS> > B [new but mapped back]: DS> > Dis: Unfortunately, mapping the old states back on to the newer DS> > diagram means that the older state code will invariable be doing DS> > things "at the wrong time". DS> DS> <Nods> DS> That's why this feels more of a hack to me than A does.
I am 100% confident that I can write a helper than will ensure that modules using the existing state map will be called at the right time, and will need no modifications to work with the new state. DS> And there's probably a bit more of an overhead involved DS> (ten traversals of the handler chain rather than four DS> for a successful request), though it's not clear how DS> significant that would be in practise. That would only be for new modules. The mapping helper would eliminate the unused states for modules using the old states. DS> > Thus, unless all the code changed All the internal agent code dealing with states will have to be changed. Modules, however, should not need to be changed. DS> If you think it's worth doing, then have the courage of your DS> convictions and go for it. Ok, so after years of being chastised for going to far, now I'm not going far enough?!? So much for my attempts at being conciliatory! -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
