Il 06/02/2011 09:25 AM, Dave Shield ha scritto: > On 1 June 2011 23:03, Wes Hardaker <[email protected]> wrote: > A possible alternative approach would be to use a simple text string, > and apply your own internal parsing of the value. > > For example, you could represent a sequence of integer values > using a string such as > > "1,1,2,3,5,8,13,21" > > As far as SNMP is concerned, this is a single string value. > Splitting it up into the separate values would be up to the > client application. > But it has the advantage over an OPAQUE encoding, > of being meaningful to the human operator looking at the > raw data. Never underestimate the utility of this!
Sure, but this would work if I had to cope with a fixed set of predefined types. This is not the case, as the user (of the application I'm writing the SNMP frontend to) could define its own types. Having to devise an encoding of arbitrary types I thought better of it and decided on using an already existing one and devised by better programmers than me ;) > > Dave -- 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
