Hi all-
In an effort to lessen the impact of this change, we are
providing two ways to be "backward compatible".
First, you could start your application setting the system
property -Dadde.auto-upcase=true which will always upcase
any ADDE request.
On an ADDE URL case by case basis, you can supply the
auto-upcase=true keyword/value pair which will just upcase
that particular request.
We hope this will suit your needs.
Don & Tom
Tom Whittaker wrote:
Hi...
It recently came to our attention that the ADDE protocol behaves
differently than we were led to believe when the AddeURLConnection class
was coded: the ADDE servers resolve names in a "case-sensitive" manner.
Although McIDAS clients (command line) always send upper-case letters,
there is now at least one site that has mixed and/or lower case letters
in dataset names.
THerefore, we are proposing a change to the AddeURLConnection class to
_not_ convert the dataset/group information to uppercase before sending
along to the server. We know that this may break existing properties
files or scripts or programs that have been set up assuming that the
conversion to upper-case would be made by AddeURLConnection before
sending the request to the ADDE server.
We welcome your comments, but feel this change must be made -- it's the
proverbial "rock and a hard place"...and we doubt we'd be able to
convince data providers to change.
tom & don
--
*************************************************************
Don Murray UCAR Unidata Program
dmurray@xxxxxxxxxxxxxxxx P.O. Box 3000
(303) 497-8628 Boulder, CO 80307
http://www.unidata.ucar.edu/staff/donm
"Time makes everyone interesting, even YOU!"
*************************************************************
