In
<cafmxnwkun21ydhzuvbvrececbcrqci1ybm_v75cqb+vkeha...@mail.gmail.com>,
on 12/26/2011
at 11:22 AM, Sam Siegel <[email protected]> said:
>Please feel free to treat this as an open ended question related to
>licensing mechanism and provided any related advice and tips based on
>experience.
Whatever mechanism you use should take into account that the user
might have to run at a DR site and that he might have to run
calendar-related code with a date other than the current date. Also,
the code should be airtight and should err on the side of giving
permission; I can think of few better ways to lose a customer than to
have a product he paid for refuse to run because of a bug in the
licensing code.
A stickier question is what you want to do about customers who are
late renewing. Some government sites are always overdue. I know that
SAS Institute cuts them some slack; I'm not sure about other vendors.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
