On 17 Feb 2007 19:54:18 -0800, in bit.listserv.ibm-main
(Message-ID:<[EMAIL PROTECTED]>)
[EMAIL PROTECTED] (Jeffrey D. Smith) wrote:
Couple of ideas pop:
1. Reclassify "license refresh" as a non-update.
An update is an update, and you can't reclassify it
as something else. (Paraphrase of old riddle: How many
legs does a dog have if you call a tail a leg? Still only
4; calling a tail a leg doesn't make it one.) If you tried
to reclassify it and fat-fingered a key, production might
stop. Then you get to explain to management how this
wasn't really an update.
2. Connect the production system to the outside world and
let the
ISV product talk to the ISV website server thing to verify
license
and dynamically update the license (e.g., "call home").
Many of these check the license very early in the IPL
sequence, often before any communications is
possible. Also, I'd worry about spyware; I don't like the
idea of software calling home.
The methods I most agree with are fail-safe, grace
periods, flat files with multiple keys (for combinations of
dates, products, and serial numbers), and a quick response
for emergency keys.
--
I cannot receive mail at the address this was sent from.
To reply directly, send to ar23hur "at" intergate "dot" com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
