On 12/29/05, Snake <[EMAIL PROTECTED]> wrote: > Distribute the compiled bytecode and not the source. > This is only supported from cf7 tho.
Sean talks about it here http://www.corfield.org/blog/index.cfm?do=blog.entry&entry=4879EDC2-F8C4-B633-C44FDABDDD608FDF since sourceless and j2ee (war/ear) deploys get confused. If you're trying to protect the code from *change* then both sourceless deploy and encryption are possibilities, though sourceless is far more robust. Decompiling is still possible, so it can be reverse engineered, but it's a lot more complicated than decrypting the CF encryption. If you're trying to protect your *intellectual property*, you'd be much better off focusing on your licensing agreement than spending time securing/obscuring your code. If you're under a simple work-for-hire (automatic default in many US jurisdictions is what I've been told), then you don't have the right to keep the code from the client once the contract is complete, etc etc, IANAL. -- John Paul Ashenfelter CTO/Transitionpoint (blog) http://www.ashenfelter.com (email) [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:227887 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
