>If an ISV doesn't use a key tied to a date and a machine serial number, what >other mechanism is there to insure there are no pilfered copies of the ISV's >product running somewhere, and the ISV doesn't have a clue?
There is the 'trust' model, which IBM uses. >From a user's perspective, if the ISV is timely in his delivery of license >keys, why is it a big deal? 1. That's a big IF. 2. In a 7/24 multi-time zone environment, getting the capability to stop all users of a product long enough to apply the keys is problematic. 3. You don't always know until the last minute (usually on a weekend), and some companies (PKWARE, for example), only work M-F/9-5. 4. If you're out-sourced, you sometimes have the service provider: a. Waiting until after they expire to tell you. b. Slow in applying them. c. Making mistakes and applying another customer's keys. The key point is it complicates an already complex environment! I can see a use for evaluation keys, but once the contract is signed, give me a permanent key, and use the 'trust' model. - Too busy driving to stop for gas! ---------------------------------------------------------------------- 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
