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.
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
thredds
archives: