Add support for storing binary DDS and DMR objects. This will require modifications to libdap so that we can 'serialize' those and additions to some of the handlers so that they can record extra information used by their specializations of those objects.
If/When the DDS can be serialized, we should be able to replace this implementation with something far better - and something that can include information in specialized BaseTypes and DDS classes.
This could just as easily be done at the end of the parse_request() method. Unless we want to support the behavior that <define> could come before <setContainer> in the request document. That is, this method is called by XMLInterface::execute_data_request_plan(), after all the elements have been parsed. jhrg 2/11/18
This command can be shortened like the setContexts command to use the NullResponseHandler since it does not normally return data to the BES's client (i.e., it's response handler uses the SilentInfo response object).
Change DataDDS to DDS if we can... Doing that will enable the handler to use this to close the library using this class. That is not strictly needed, but it would make both the DDS and DataDDS responses work the same way.
Change DataDMR to DMR if we can... Doing that will enable the handler to use this to close the library using this class. That is not strictly needed, but it would make both the DMR and DataDMR responses work the same way.
Member print_attr (hid_t type, int loc, void *sm_buf)
Due to the priority of the handler work, this function will not be
re-written in this re-engineering process. KY 2011-Nov. 14th