note 50058 added to function.eval

Sorry if this not the way this forum should be used. I develop PHP code in my own server and port them out to my customer's server at the end. One obvious problem is source code protection. I am aware of serveral commercial solutions but I just want to try the following method with eval() first. I'd appreciate if anyone would comment on whether this is a feasable route. I intend to use eval() to achieve 'code encryption'. That is, I will 'hide' or 'encrypt' the source code before I deliver it to customer's server. Then, with password or other mechanism, I will de-cipher the code at the run time using eval(). Is there a big issue with this trend, if we are talking about 1,000 php files? Thanks in advance... ---- Manual Page -- http://www.php.net/manual/en/function.eval.php Edit -- http://master.php.net/manage/user-notes.php?action=edit+50058 Delete: added to the manual -- http://master.php.net/manage/user-notes.php?action=delete+50058&report=yes&reason=added+to+the+manual Delete: bad code -- http://master.php.net/manage/user-notes.php?action=delete+50058&report=yes&reason=bad+code Delete: spam -- http://master.php.net/manage/user-notes.php?action=delete+50058&report=yes&reason=spam Delete: useless -- http://master.php.net/manage/user-notes.php?action=delete+50058&report=yes&reason=useless Delete: other reasons -- http://master.php.net/manage/user-notes.php?action=delete+50058&report=yes Reject -- http://master.php.net/manage/user-notes.php?action=reject+50058&report=yes Search -- http://master.php.net/manage/user-notes.php