[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[THREDDS #JUE-335127]: Questions about Thredds

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [THREDDS #JUE-335127]: Questions about Thredds
  • Date: Tue, 20 Dec 2016 16:22:55 -0700
Hi Herbert,

You seem to be describing server-side functions. Unfortunately, THREDDS doesn't 
currently support them. There's certainly a compelling use case there, but 
there are pretty thorny security issues to work out as well.

You may be interested to know that Hyrax supports them [1]. However, it looks 
like functions can only be added at install time of the server, not runtime.

As for read performance, the 100TB aggregation will certainly take longer the 
first time its data is accessed. However, subsequent acceses should benefit 
from caching and be much faster.

Cheers,
Christian

[1] http://docs.opendap.org/index.php/Hyrax:_Server_Side_Functions

Ticket Details
===================
Ticket ID: JUE-335127
Department: Support THREDDS
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.