Subject: | |
From: | |
Reply To: | |
Date: | Mon, 27 Jan 2003 19:00:30 -0800 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Ciupdate can mess you up if you have extended sort keys (sorting by another
field immediately after the sort key), and your applications depend on it.
So our standard is to leave it 'allowed', and some applications that DON'T
go anywhere near extended sort keys do in fact do what Wirt thinks no one
has ever done......
Dave ('but I do like the idea of enhancing Image as much as possible
before...') Powell
----- Original Message -----
From: "Wirt Atmar" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Monday, January 27, 2003 3:25 PM
Subject: Re: [HP3000-L] SIGIMAGE Update: HP R&D Lab still open
> Ken asks:
>
> > (3) As we close in on end-of-HP-sales just over nine
> > months from now, the Lab is wondering if there are any
> > "last call" low / medium effort, low risk enhancements
> > that the user community would like them to do.
>
> Absolutely. Change the CIUPDATE setting in IMAGE to ON as the default.
This
> is the manner the setting should be set as IMAGE heads into the sunset
(and
> possibly a brighter future). Estimated lab effort: 3 minutes.
>
> CIUPDATE is currently set to the ALLOWED condition -- the functional
> equivalent to OFF because no one I'm sure has ever programmed an
application
> to take advantage of the ALLOWED setting. CIUPDATE is set this way only
> because CIUPDATE was the first enhancement done to IMAGE in 15 years and
> everyone was being excessively cautious at the time, but I argued then
that
> it was not necessary, and it's certainly not necessary now.
>
> Wirt Atmar
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
>
>
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
|
|