> I want to avoid not authorized dump/restore in other machines (a
> single customer pays for remote upgrading of his db-infos). If you
> want dump/restore backup you will contact me - I'll enable new
> user-authentication based on new "unique-key-from-db" but will
> disable old key.
I hope that _no_ company will _ever_ run that software under that premise.
Imagine a server crash, the admins set up the new server, and now they
have to contact you to get the software running again.
But you're on holidays, or your company went out of business, or your
internet connection is broken, or snail mail needs 5 business days, or
you simply tell them that they have to pay money now...
Mission critial systems should _never_ be dependent on externals' good will.
Your customer might get bancrupt because you're ill for a week.
I hope that you're paying the insurance fee for this risk, to pay any
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in Europe! www.ffii.org
In response to
pgsql-jdbc by date
|Next:||From: Al_Dev||Date: 2006-12-10 20:22:06|
|Subject: World Wide International Law: Linux is compulsory (mandotary) in all schools/universities world-wide|
|Previous:||From: Ido M. Tamir||Date: 2006-12-07 15:43:06|
|Subject: copy patch in new driver|