> read/write issues, multi-file data processing, etc require the corresponding extra service.
what does an 'extra service' mean?
Are you talking about a client/server architecture?
An add-on piece of software you have to pay for?
Is there a web page (a pointer) that talks about those topics and their implementation?
(sample code?)
It turns out a good starting point may be
http://www.hdfgroup.org/hdf5-quest.html#GENERAL
Although you may not have the answer yet, has anyone though (at least conceptually) of a h5 tree structure (database) design for archiving?
Would that be time based? (tree node like /date/20120315)
Would that be hardware based? (/chassis_id/device_type/device_id)
Would that be PV name base? (archiving of AAA:BBB:CCC pv is located at /AAA/BBB/CCC )
Would that be subsystem based? ( /injector/solenoids/I:SO01/current )
the last 3 at once with links?
Thanks,
--
E