This might unfortunately be a sticking point. We're in a position with one of our clients where we simply can't trust them not to tamper with the code we've written for them. This would be ok, but anything that goes wrong with it they blame us for even when it's their fault. So, we use IonCube Encoder on all the work we do for them before it gets uploaded to their server.
If we're not allowed to do that under the license, then I reckon the directors will be saying no to Cake (and all other open-source frameworks, for that matter). We're happy to respect copyright and leave those messages in place, but the code itself needs to be protected from tampering. It's a bit of a bugger really! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to cake-php@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
