I've been waiting for someone to come up with this idea...
This is simple, use the code protection on the chip.  It is there to protect
the code.

-----Original Message-----
From: wouter van ooijen & floortje hanneman [mailto:wf@XS4ALL.NL]
Sent: Tuesday, January 08, 2002 10:03 AM
To: PICLIST@MITVMA.MIT.EDU
Subject: Re: [PIC]: Delivering Software


For a somewhat restricted case this schedule can reduce the benefit of
cheating:

1- customer issues order
2- programmer makes code, delivers one code protected chip
3- customer verifies correct working
4- customer pays
5- programmer sends source code

There is no way that the customer gets his code without paying (although he
might refuse to pay after the programmer has done the hard work, but then
the customer will have just one lousy chip). The programmer can collect the
cash and then refuse to send the code - but what is his benefit? He has
already written the (accepted) code, so there is no benefit in not sending
the code - only the risk of losing his good name.

Wouter

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics