On Tue, 05 Oct 2004 14:43:49 +0100 John wrote: JN> [EMAIL PROTECTED] said: JN> > It seems to me that it might also make sense to move the host_ctl stuff JN> > into the transport code itself. JN> JN> I like this idea a lot. Probably the right thing to do would be to add JN> a method to the transport object that will perform the appropriate JN> checking if non-NULL. NULL would imply "always succeeds" which is JN> probably appropriate for AAL5, IPX, callback. This is a much simpler JN> test than "formatted string contains '['"!
Exactly what I had in mind, though I also considered simply having the host_ctl call in the read/accept function. I don't recall if the transport structure has a flags member, but if it does, a flag for whether or not to automatically apply the call would be nice. Or rather, the default should probably be to call it, with a flag to disable. In that case, the function pointer, so the user could call the check later, would be best. -- Robert Story; NET-SNMP Junkie <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. ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Net-snmp-coders mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
