> > This API is limited to returning global information about HDS. If it had
> > an HdsLoc argument it could be expanded at some point in the future if
> > necessary to also return information about a specific locator. That would
> > make it even more like grpInfoI.
>
> Just wondering what extra information, about a locator, you might like to
> see. The full name and path can be obtained by DAT_MSG, and that's about
> all I can imagine would be useful (in addition to the proposed info). The
> internals of the various structures look less useful. (or also can be
> gotten though queries on a locator, name, dimensionality etc.).
The suggestion was mainly because including a locator parameter would
provide for future expansion. Off the top of my head, what about enquiring
the number of primary locators associated with the container file?
David
|