Jordan Michaels wrote:
If you have a situation where you want to distribute an encrypted version of the actual OpenBD engine (to hide what platform your app is running on, or various other reasons), then you need to look into the dual-licensing option available from NewAtlanta.
Technically speaking if you *distribute* a CFML application that includes the OpenBD runtime, then your CFML application code must also be open sourced under the GPL. Note that this does not mean that to *run* an application on OpenBD the CFML application must be GPLed. This only applies if you *distribute* the application. If you're just running CFML code on OpenBD the CFML application does not need to be open source.
There are some points of discussion around this I suppose, specifically whether or not OpenBD is an "interpreter" (this came up in an earlier thread), but on the face of it the GPL would dictate that if you're distributing an application as a single unit containing OpenBD, you'd have to GPL your application code.
You most certainly could distribute your application code separately from OpenBD, meaning your application is designed to run on OpenBD but the distribution itself does not contain the OpenBD runtime, and then your CFML application would not have to be released under the GPL.
All this is a bit of a moot point, however, since running encrypted CFML code is not supported on OpenBD, and as far as I know we have no plans to support that since it goes against the open spirit of the project. You could certainly run encrypted code on the commercial edition of BlueDragon though.
-- Matt Woodward [email protected] http://www.mattwoodward.com/blogPlease do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
smime.p7s
Description: S/MIME Cryptographic Signature
