Re: Self Destruct code
| From: | Miguel Cruz | Date: | Tue, 07 May 2002 18:22:18 +0000 |
| Subject: | Re: Self Destruct code | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-96471@lists.php.net to get a copy of this message | ||
On Wed, 8 May 2002, Justin French wrote:
> I don't believe this is the right way to do things, and really, anything you
> "break" can be spotted, fixed, patched and repaired. Sure, it might piss
> them off for a few days, but it aint a solution.
I don't agree with destroying code or data, but a time lock that stops it
from working after a certain period of nonpayment seems fine.
Chances are they'll have to hire someone else to fix it. Make sure you put
plenty of comments in there for the next person explaining that the reason
they're in there is because you didn't get paid. At least that'll make the
next person think twice.
Really, though, if you haven't been paid for something, and you don't have
the sort of relationship where you're confident you will be, don't deliver
it in a way that gives them control. Keep it on a server where you have
the password. Or perhaps keep some crucial files/functions on your server.
miguel