Il 06/06/2011 10:45 AM, Dave Shield ha scritto: >[...snip...] >> What I'm thinking is adding a 'X' type flag meaning something >> like "the data is to be sent as 'opaque' and here it follows the data >> itself ber-encoded and written as an hex string." > > Yes - that seems a perfectly sensible extension. > I'm not sure how widely useful it would be to anyone > else, but it wouldn't do any harm either. > > I think that about the only code you'd need to touch > would be 'snmp_add_var' (in snmp_api.c), plus > the type validation in snmpset itself. > > Dave This is exactly how I was plaining it, plus checking uses of snmp_add_var elsewhere in the code (just to be sure, the only 'visible' difference would be that passing the '=' flags for a name naming an Opaque variable will try to interpreter the value as an hex string instead of failing).
Should the code be under a defined(NETSNMP_WITH_OPAQUE_SPECIAL_TYPES) switch? Leo -- Leo Cacciari Aliae nationes servitutem pati possunt populi romani est propria libertas ------------------------------------------------------------------------------ Simplify data backup and recovery for your virtual environment with vRanger. Installation's a snap, and flexible recovery options mean your data is safe, secure and there when you need it. Discover what all the cheering's about. Get your free trial download today. http://p.sf.net/sfu/quest-dev2dev2 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
