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.
>From: Jerrold Robaidek <address@hidden> >Organization: SSEC >Keywords: 200405211957.i4LJv7tK020887 McIDAS ADDE Hi Jerry, >I recall that a few years ago the folks at Unidata requested the >ability to restrict ADDE access by dataset name (rather than all >datasets on a machine.) I also seem to recall you saying that >Unidata was going to pursue this on its own since at that time >this was not a very high priority for SSEC. Right. Our desire was even more restrictive, however. I want to be able to restrict datasets down to the descriptor level. This would allow blocking of remote access to things like Lightning data which is a descriptor under RTPTSRC. >Did Unidata pursue this? Did Unidata ever solve this problem for >themselves? ... is this in the Unidata version of McIDAS? The ability is there in the ADDE servers I wrote. I did not add the ability to subrestrict in the primay ADDE servers. The job of adding the restriction ability should be straightforward, however. Is there a general acknowledgement that this would be a welcome feature now? >Thanks for any information you can provide. No worries. Cheers, Tom -- NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publically 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.