Il 06/06/2011 06:47 PM, Robert Story ha scritto: > On Tue, 31 May 2011 12:07:48 +0200 Leo wrote: > LC> If I understand correctly the documentation and the code, with this > LC> approach I would have to write routines for encoding/decoding the > LC> application data types into a buffer accordingly to some ASN.1 encoding > LC> scheme (presumably BER or CER). > > Seems like an awful lot of extra work to me. Why not just pass blobs of raw > data with OCTET STRINGs? Because the systems on the two ends of the communication tunnel could have, e.g. different endianess or different views on how struct's fields should be packed. More to the point, even if the systems where identical, as I have sequences (with dynamic length) and not arrays (with fixed length) I'd have to code the length somehow. Sure, I can do it, but ASN.1 already do this for me and it's standard :)
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
