libdap
Updated for version 3.20.6
libdap4 is an implementation of OPeNDAP's DAP protocol.
|
Modify the D4 serialize code so that it supports the true/false behavior of read() for arrays.
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
Modify all of the stock handlers so they conform to this!
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.
All the methods that use names to identify variables should have counterparts that take BaseType pointers.
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...
Move, in some sense, the d_map_vars up to Constructor. Look at using Constructor's _var field for these.
Along the same lines as the previous item, consider removing the Part enum and adopting the convention that the first variable added is the array and any subsequent variables are maps.
Update documentation: get_cache_response() now also serves as is_url_in_cache() and is_url_valid() should only be called after a locked cached response is accessed using get_cahced_response(). These lock the cache for reading. The methods cache_response() and update_response() lock an entry for writing.
Check that the lock-for-write and lock-for-read work together since it's possible that an entry in use might have a stream of readers and never free the 'read-lock' thus blocking a writer.