OpenBD must remain open at all times. Even if you pack it up and distribute it, OpenBD must to remain open.
You can do whatever you want with your own CFML, but the engine always has to be open. It is bound by the GPLv3. 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. Warm regards, Jordan Michaels Vivio Technologies http://www.viviotech.net/ Open BlueDragon Steering Committee Adobe Solution Provider DetailsDotAt wrote: > Are their any license restrictions about site portability? > > I'm looking at a site I just setup using the R2R package, and it looks > like all I need is Java 1.6 installed. > > Once I have the site tested and functioning, could I encrypt the code, > create a batch file to setup the site as a service (I already have the > code) and have a script make minor changes to the .xml so that someone > could literally just install the app and have it run in their browser > out of the box??? I already figured out how to rename the service to > the webapp name, so to the end user it would look like a legit > application that just runs using a browser. > > I'm not ready to jump feet first into this just yet, but I'm curious > about the viability of such a thing and if it is feasible. > > > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
