On Mon, 17 Oct 2005 11:56:17 -0700 Srini wrote: SK> From the mib impletation code we return the values in host order and we SK> believe snmp stack should format the values in network byte order and SK> send on wire.
What are the types of the object involved here? Question to core developers: do we have a policy on byte order? If not, we should, as this is the second time endian-ness has bit us recently. It would seem obvious that integer based types should be in host byte order, and the library will convert to/from network byte order on sending/receiving. The IpAddr type complicates things a bit. It's integer based, but defined as being in network byte order. Should this type be treated like all other integer types (ie kept in host byte order), or do applications need to deal with it explicitly? The new IpAddress TC adds more confusion to the mix, as it is based on octet strings. We should probably have an api for converting 4 byte IPv4 addresses to/from this TC. -- 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. ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
