Server side processing: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary
No edit summary
 
Line 1: Line 1:
<pre>
Bare-bones list of ideas:
On Dec 8, 2009, at 7:20 AM, H. Joe Lee wrote:
# RSS feed for broadcasting changes in files/datasets served by Hyrax
 
# a per-directory config file for various handler parameters (like those that control how the HDF5 handler treats files)
Hi, James!
# checksum for data returns
 
# a clone of Matlab's 'find' function
I found what was wrong. Long time ago, I commented out the following
# plotting for the HTML form interface
line to make handler work for older version and did not put it back:
 
  dds_table.set_dataset_name();
 
Commenting the line out inserted "virtual" at the end of each DDS output. :-)
 
Ah.
 
 
By the way, do you think it's possible to modify the handler's
behavior based on an input file (e.g, XML)  per current working
directory basis?
 
It probably would. Is there an actual need for this?
 
For example, the two directories d1 and d2 both serve HDF files but
they have different models. Specifically,
 
1) d1 has mapping.xml, f1.hdf, and f2.hdf
2) d2 has mapping.xml, g1.hdf, and g2.hdf
 
When handler is serving f1 and f2, it looks for "mapping.xml", reads
it and generates output that are slightly different from the default
one based on the rules specified in the "mapping.xml" file.  Likewise,
when it is serving g1 and g2, it looks for "mapping.xml" and changes
behavior accordingly.
 
 
Finally, I wish Hyrax can generate new RSS feeds automatically on
every directory it serves whenever a new dataset is added in that
directory. I'm not sure it should be done by the handler or other
Hyrax module.
 
This sounds pretty interesting.
 
Best Regards,
</pre>

Latest revision as of 22:58, 29 December 2009

Bare-bones list of ideas:

  1. RSS feed for broadcasting changes in files/datasets served by Hyrax
  2. a per-directory config file for various handler parameters (like those that control how the HDF5 handler treats files)
  3. checksum for data returns
  4. a clone of Matlab's 'find' function
  5. plotting for the HTML form interface