search

Kingside / odinmobile

Automatically exported from code.google.com/p/odinmobile
0 stars 0 forks source link

Standardized format seed #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
In all of the cases, there is no standard written to follow for hashing (that 
is clear to me anyways)

Example for mac address:
I can hash the actual bytes, hex codes in ascii Upper, or ascii lower, hex 
codes in ascii with "-" or ":" separators; it all depends on how I receive the 
mac address.

If there were a prescribed standard, it would prevent different implementations 
from generating different hashes for the same ID.

"Mac address must be the raw bytes" or "Mac address must be the lower case 
ascii hex codes without a separator".  That keeps people like me from messing 
it up.

The same goes for the other identifiers, although there is a standard API call, 
it would be nice to have a standard format to ensure we are making a standard 
ODIN hash.

Original issue reported on code.google.com by syna...@gmail.com on 2 Apr 2012 at 2:46

GoogleCodeExporter commented 9 years ago 
I really didn't mean for this to be a "Defect" but I wasn't given an option to 
classify it as something else.

Original comment by syna...@gmail.com on 2 Apr 2012 at 2:47