Hello- any experience in storing a GUID efficiently in HDF5? It would probably be handled in the application as part of a struct (compound data type).
4byte-2byte-2byte-2byte-6byte
The standard textual representation is {12345678-1234-1234-1234-1234567890AB}.
Warm Regards,
Jim
Jim, how are you? Unless the components (segments) mean anything in your application
and you'd want to make them visible independently, I'd create an 128-bit integer type.
(H5Tcopy a pre-defined integer type, H5Tset_precision(.,128), H5Tset_order(.,H5T_ORDER_BE))
I'd use big endian byte order as RFC 4211 suggests. You'll need to write a few conversion function
to render it in the segmented string/hex formats...
Best, G.
From: Hdf-forum [mailto:hdf-forum-bounces@lists.hdfgroup.org] On Behalf Of Rowe, Jim
Sent: Friday, April 11, 2014 5:23 PM
To: HDF Users Discussion List
Subject: [Hdf-forum] storing a guid in hdf5?
Hello- any experience in storing a GUID efficiently in HDF5? It would probably be handled in the application as part of a struct (compound data type).
4byte-2byte-2byte-2byte-6byte
The standard textual representation is {12345678-1234-1234-1234-1234567890AB}.
Warm Regards,
Jim
