Hi Andy, Thanks for your email! Responses inline below:
> In the product server documentation it states that the service can > "transform products from proprietary formats and into Internet standard > formats or run other transformations, all without impacting local stores or > operations." > > I was wondering what enabled this open-ended functionality. From what I can > tell, the idea is that you simply create your own implementation of the > QueryHandler interface and do all of the data fetching/transformation there. > > Is that the case? You got it! A QueryHandler is a facade interface for numerous underlying "connectors" that link you to proprietary formats, and allow you to serve them back to your users with ease. We have a number of projects that have deployed QueryHandler interfaces across their projects, some of which have made it back into OODT-land and some of which haven't. Some really good examples: XMLPS - EDRN - an XML configurable, Product and Profile server implementation that delivers out data from underlying JDBC accessible RDBMS'es. OFSN Handler - PDS and CDX - an XML configurable Product server that delivers out underlying file-based data using a standard REST protocol (the PDS OFSN protocol described here http://oodt.jpl.nasa.gov/pds-client/guide/product/) OPeNDAP PS - VODC and CMDS - an XML-configurable way to dump out data and metadata from underlying OPeNDAP and THREDDS accessible catalogs. HTH! Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
