On Tue, Oct 29, 2013 at 4:32 PM, Tom Browder <[email protected]> wrote: > I think I understand now. How about something like this: > > As DB V5 goes now, there are two indicators for the end of the > attribute block: two NULLs in a row AND total length > (Attribute_Length). If we use the space AFTER the double NULLs for > binary attributes that should be relatively straight forward. If the > occurrence of the last of the NULL pair is at the Attribute_Length > byte we are done, else continue reading binary attributes until the > last byte read is the Attribute_Length byte. The binary attribute > chunks after the double NULL could be: > > <ASCII key> NULL <unsigned int attr length> <attr length bytes...> > [repeat for all binary attributes] > > Completely backwardly compatible! We would set the AWid flag to > ensure the unsigned int for attr lengths was adequate for the longest > binary attribute.
I've added that description as "PROPOSED" in the DB V5 doc. BTW, the DB V5 doc repeatedly mentions a WWW registry of attribute key names. Isn't it time to have that clearly visible on the site? Best, -Tom ------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
