Yes, I've had that thought also. I believe that the question you suggest will probably the foundation of the main course I'll take. For what possibilities are there really to hide anything in plain text that anyway will reside on third-party servers. (rhetorical question) You can never know what network technicians, system adminitrators or web developers get hold of the code.
Open-source, I believe, will be the only direction. This however, yields another question for me. If not protecting the "intellectual content" (now, I have serious doubts to whether one can call PHP code exactly that), then it must come down to protecting hard-to-get PHP coding knowledge. As for retrieving a few records from a MySQL database, it is trivial enough for anyone to master. But considering all the server extensions that are produced (*hint*) with PHP, there should be the need to protect the knowledge of what solutions one use in Intra networks. There within, I think, lies my true problem... Thanks for your answer, strengthens my own point of view! VPeO <snip> It depends on what your definition of security is! :) Actually this is very much a hot-button topic in PHP circles. Many use code obsfuscators. There is at least one very young PHP compiler (priadoblender). Several folks place copyright/left/center data in each script. I guess it comes down to asking, "what is it you wish to protect?". Many PHP developers who compile (pun intended) large projects/products release them as open-source, so they have no desire to hide code. </snip> -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
