Re: thredds.catalog API

• To: Darren Hardy <dhardy@xxxxxxxxxxxxx>, Ethan Davis <edavis@xxxxxxxxxxxxxxxx>
• Subject: Re: thredds.catalog API
• From: John Caron <caron@xxxxxxxxxxxxxxxx>
• Date: Tue, 22 Aug 2006 16:32:04 -0600

Hi Darren:

Yes, we have noted the same problem. We originally envisioned catalogs only be 
written as XML, but it turns out there's various use cases for object creation. 
The Impl classes are in fact intended for this purpose.

Ill add thredds.datatype to the public javadocs, thanks.

Darren Hardy wrote:

Hi John,

We met at the discovery workshop at your office in Boulder back in May. I'm working on some software (DAPADL project) that will generate THREDDS catalog content.

I've downloaded the NetCDF library, but I have some comments about its public API.

http://www.unidata.ucar.edu/software/netcdf-java/v2.2.16/javadoc/ index.html

So, I'm wondering what process you use for enhancement requests and/ or code contributions. I'm finding that the API doesn't support the generation of catalogs as well as the reading of catalogs. The factory, for example, doesn't provide methods to create new InvCatalog/InvService/InvDataset objects, so I have to explicitly use their Impl classes. The thredds.datatype package is also not in the API javadoc, but it's required for the catalog element's expires attribute.

Thanks,
-Darren
--
Darren Hardy
Ph.D. Student
Bren School of Environmental Science & Management
University of California, Santa Barbara
dhardy@xxxxxxxxxxxxx
www.bren.ucsb.edu/~dhardy



--
Darren Hardy
Ph.D. Student
Bren School of Environmental Science & Management
University of California, Santa Barbara
dhardy@xxxxxxxxxxxxx
www.bren.ucsb.edu/~dhardy