Re: question

From: Date: Tue, 16 Feb 1999 22:27:58 +0000
Subject: Re: question
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-4126@lists.php.net to get a copy of this message
There are no plans to add such features into PHP 3.0. A limited way of protecting your code will be introduced in PHP 4.0, for further details, look at http://www.zend.com . Zeev At 00:17 16/02/99 -0600, Ryan wrote: >Hi, > >I'm not sure if this has been asked before since I am a recent subscriber >to the list, but has anyone thought about writing some kind of >encoding/encryption for the php files themselves? Perhaps a pre-compiler? > >For developers who are selling their work in PHP, it would be very useful >to be able to give people pre-compiled versions of the pages containing php >- perhaps defined with a special extension, such as .cphp or something, >that could be parsed by the php libs. > >If it was precompiled in some fashion, it would probably even be faster to >access. Even if it wasn't precompiled, perhaps some kind of encryption >function could be added that would decrypt the page, then parse the php >script, based on a key pair provided by the author. The encryption wouldn't >even have to be that great, just enough to stop the average user from >messing about with the code and scripting. > >The reason for this suggestion is that if someone is selling their work, it >would be nice not to just hand over the source and everything to the end-user. > >Thanks, >Ryan > >Ryan Addams >Senior Programmer, Saper Media Group >http://www.sapermedia.com > >-- >PHP Development Mailing List http://www.php.net/ >To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net >For help: php-dev-help@lists.php.net > > > -- Zeev Suraski <zeev@zend.com> http://www.zend.com/ For a PGP public key, finger bourbon@netvision.net.il -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net

« previous php.dev (#4126) next »