You can't protect your source code. You can encrypt it, but
it can be de-crypted by anyone who really wants to do it. If
you re-considered being an ASP for the product, that might be
safe (but what a pain).
With CF6, this might change, since I understand CF code will
be compiled. I'm not sure if it's done once as it's deployed,
or done on the fly, but maybe there is hope there.
-Erik
> -----Original Message-----
> From: Sean Blenkhorn [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, December 20, 2000 10:13 AM
> To: Fusebox
> Subject: OT: source code protection....
>
>
>
> Hey all...
>
> We are in the early stages of designing a web product (piece
> of software).
> We are thinking of developing it in Cold Fusion for speed to
> market. Now we
> don't want to necessarily pigeon hole ourselves to being an
> ASP for this
> software, instead, we would also potentially like to sell the
> software and
> have users run it on their corporate LAN. Our problem is
> that if we do sell
> the software so that a client can install it on their
> Intranet/Extranet...
> how do we protect the source code?? (assuming we are selling
> to a client
> that has CF... or is ok with the licensing fees). What does everyone
> think?? Is there better options for us?? Or is there ways
> to protect CF
> code from people tinkering??
>
> Thanks,
> Sean
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
