NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: [thredds] Nesting serviceType="Compound"??


Ethan,

Another question, about service inheritance.

Example:

    <dataset name="level1" ID="SingleFileWcs">
        <serviceName>dap</serviceName>

         <dataset name="level2_a" urlPath="wcs/foo" ID="wcs/foo" />
         <dataset name="level2_b" urlPath="wcs/foo" ID="wcs/foo" >
            <serviceName>otherService</serviceName>
         </dataset>
    </dataset>


Is the dataset "level2_a" associated with the "dap" service??
Is the dataset "level2_b" associated with the "dap" service??
Is the dataset "level2_b" associated with the "otherService" service??


Nathan


On Dec 1, 2009, at 9:44 AM, Ethan Davis wrote:


Yes, any service defined in a catalog can be directly referenced by a
dataset/serviceName element.

This is true whether the service is a solitary service, a nested
service, or a compound service. The only special case is when a compound 
service is referenced, then all contained services are available.

Ethan

Nathan Potter wrote:



And one last question:

If a thredds:service is defined as part of a thredds:service of
serviceType="Compound" can it be referenced directly in the catalog?

Example:

<service name="all" serviceType="Compound" base="">
  <service name="HTTPServer" serviceType="HTTPServer"
base="/thredds/fileServer/" />
  <service name="dap" serviceType="Compound" base="">
<service name="ncdods" serviceType="OPENDAP" base="/thredds/ dodsC/" /> 
    <service name="hyrax" serviceType="HTTPServer"
base="/opendap/hyrax//" />
  </service>
</service>

   <dataset name="fnoc1.nc" urlPath="coverage/fnoc1.nc"
ID="coverage/fnoc1.nc">
     <datasize units="bytes">2590804</dataSize>
     <date type="modified">2009-08-06T23:48:40</date>
     <serviceName>ncdods</serviceName>
   </dataset>




Nathan


On Dec 1, 2009, at 8:45 AM, Nathan Potter wrote:




Greetings,

2 quick questions for clarification:

When defining the thredds:service, is it allowed to have nested
service elements with serviceType="Compound"?

Example:

<service name="all" serviceType="Compound" base="">
  <service name="HTTPServer" serviceType="HTTPServer"
base="/thredds/fileServer/" />
  <service name="dap" serviceType="Compound" base="">
    <service name="ncdods" serviceType="OPENDAP"
base="/thredds/dodsC/" />
    <service name="hyrax" serviceType="HTTPServer"
base="/opendap/hyrax//" />
  </service>
</service>

And similarily can a a service of thredds:serviceType="Compound" be
referenced from another thredds:service of serviceType="Compound"??


Example:

  <service name="dap" serviceType="Compound" base="">
    <service name="ncdods" serviceType="OPENDAP"
base="/thredds/dodsC/" />
    <service name="hyrax" serviceType="HTTPServer"
base="/opendap/hyrax//" />
  </service>

<service name="all" serviceType="Compound" base="">
  <service name="HTTPServer" serviceType="HTTPServer"
base="/thredds/fileServer/" />
  <service name="dap" />
</service>



Nathan



= = =
Nathan Potter                        ndp at opendap.org
OPeNDAP, Inc.                        +1.541.231.3317






= = =
Nathan Potter                        ndp at opendap.org
OPeNDAP, Inc.                        +1.541.231.3317





= = =
Nathan Potter                        ndp at opendap.org
OPeNDAP, Inc.                        +1.541.231.3317
  • 2009 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the thredds archives: