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

• To: Nathan Potter <ndp@xxxxxxxxxxx>
• Subject: Re: [thredds] Nesting serviceType="Compound"??
• From: Ethan Davis <edavis@xxxxxxxxxxxxxxxx>
• Date: Tue, 01 Dec 2009 10:01:56 -0700

Hi Nathan,

Nathan Potter wrote:
> 
> 2 quick questions for clarification:
> 
> When defining the thredds:service, is it allowed to have nested service
> elements with serviceType="Compound"?

Yes.

> 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"??

No. The catalog spec doesn't support a service referencing another
service. (That is a good idea though.)

Ethan

> 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

• References:
  • [thredds] Nesting serviceType="Compound"??
    • From: Nathan Potter