Quoting Joey deVilla <[EMAIL PROTECTED]>: > [EMAIL PROTECTED] wrote: >> There isn't any reason, other than performance, why we can't run this >> for testing and noT use zend, is there? > > Other than performance, there's the "safety" issue. Encoding some files > with Zend Encoder creates a safety net that prevents the unintentional > editing of core files. Aside from the obvious reason of preventing > people from accidentally "breaking" the application, there is the issue > of kkeping CCS upgradeable: you can modify the "uncompiled" files > without fear of making your CCS app non-upgradeable.
The safety issue isn't a big concern of mine, but PRACTICAL security will certainly be and that has nothing to do with zend compilation. I have a few questions on that once I have the basic operation and customization figured out. Far now, I hope that the "safety issue" will not block the initiated process of publishing all the source code. IMO, sometimes you need to shoot yourself in the foot to create a learning opportunity. :D > In an upcoming entry in the CCS blog (http://ccs.tucows.com), I'll > provide a list of which files are "compiled" and which are "uncompiled". It might be interesting for reference but on a unix system a quick and dirty - egrep -lr '<?php @Zend;' topLevelCCSfolder - will give you a list of 172 compiled files. Thanks all and enjoy what's left of your weekend, ed _______________________________________________ domains-gen mailing list [email protected] http://discuss.tucows.com/mailman/listinfo/domains-gen
