Todo List

Member libdap::Constructor::serialize (D4StreamMarshaller &m, DMR &dmr, bool filter=false) override
  See notebook for 8/21/14
Class libdap::D4Enum
  Note the hack to remove the union...
Member libdap::D4Group::transform_to_dap2 (AttrTable *parent_attr_table) override
  Fix the comment.
Member libdap::D4RValue::value (DMR &dmr)
  Could move the operation that wraps a constant in a BaseType to this method while providing other ways to access the value(s) (methods to determine if the rvalue is a constant and what DAP type it is, e.g.). This would provide an optimization for the filter evaluator which may access the values many times. We might also modify the server side functions so they could access constant values more efficiently.
Member libdap::DDS::mark_all (bool state)

  These methods that use the btp_stack to keep track of the path from the top of a dataset to a particular variable can be rewritten to use the parent field instead.

  All the methods that use names to identify variables should have counterparts that take BaseType pointers. */ bool DDS::mark(const string &n, bool state) { unique_ptr<BaseType::btp_stack> s(new BaseType::btp_stack);

Member libdap::DODSFilter ()
  Add methods to provide a way to set all of the parameters this class contains. They can currently only be set using the argc/argv command line parameters.
Member libdap::establish_timeout (FILE *stream) const
  When the alarm handler is called, two CRLF pairs are dumped to the stream and then an Error object is sent. No attempt is made to write the 'correct' MIME headers for an Error object. Instead, a savvy client will know that when an exception is thrown during a deserialize operation, it should scan ahead in the input stream for an Error object. Add this, or a sensible variant once libdap++ supports reliable error delivery. Dumb clients will never get the Error object...
Class libdap::HTTPResponse
  Maybe refactor so that the header parsing code is here and not in HTTPConnect?
Member libdap::HTTPResponse::HTTPResponse (std::fstream *s, int status, std::vector< std::string > *h, const std::string &temp_file)
  Decide on how the temp files fit into DAP4
Member libdap::Response

  Add a test to make sure that the required arguments are given.

  We need to rethink the ancillary file/directory stuff. I don't think it's ever been used...

  If the code that parses the MIME headers was moved from Connect and HTTPConnect to this class and its children, it would be easier to build a FileConnect class (or maybe the specifics of the connection type could be held in the Response object and HTTPConnect and the to-be-written FileConnect would not be needed).