Aparajita Fishman wrote:
A change of IP address would normally be a planned event and so new
keys can be arranged in good time. A change of hardware, in my
experience, usually happens when catastrophic failures have occurred.
At a time like that, you don't really want the extra problem of
having to get new keys for Active4D.
Would others agree?
Our primary IP address hasn't changed since we've used A4D. I routinely
swap servers to perform maintenance. I've also had NIC failures. In
these cases changing a replacement machine's IP to match the license is
easy. Downtime is minimal.
Your MAC-based license mechanism might work if:
(a) A legitimate license key is installed
(b) It no longer matches its registered MAC Address
(c) Its timeout is set to a value larger than the 8 hour development
timeout. This value would be sufficient to get a new key.
(d) Active4D could send you (and the licensee) a notification that a
license mismatch occurred.
-- Brad Perkins
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
