Re: Commercial app demo

2000-02-11 Thread Gidon Wise
I must confess that I wrote a buggy but small script that makes perl code unreadable. I promise. It basically removes comments, excess white space, and changes all the identifiers to weird names. It was during a silly moment and I'm not proud. But, if you can get it to be any uglier, we can

Re: Commercial app demo

2000-02-11 Thread Ask Bjoern Hansen
On Wed, 9 Feb 2000, Matt Sergeant wrote: Has anyone delivered a commericial mod_perl application before? If so, how do you handle demo versions, preferably with expiration dates? [...] Contracts, Trust and Good Relations to the customer. Being a small/one man company you could make it a

Re: Commercial app demo

2000-02-10 Thread Matt Sergeant
On Thu, 10 Feb 2000, Fabrice Scemama wrote: There's another way. We can't build pre-compiled modules easily, but even when you code in C or Java, desassemblers can extract some source from the binaries you deliver. As far as perl scripts are concerned, a workaround consists in trivially

Re: Commercial app demo

2000-02-10 Thread G.W. Haywood
Hi there, On Thu, 10 Feb 2000, Fabrice Scemama wrote: There's another way. We can't build pre-compiled modules easily, but even when you code in C or Java, desassemblers can extract some source from the binaries you deliver. As far as perl scripts are concerned, a workaround consists in

Commercial app demo

2000-02-09 Thread Matt Sergeant
Has anyone delivered a commericial mod_perl application before? If so, how do you handle demo versions, preferably with expiration dates? One thought is to simply xor encrypt some of the modules when the user downloads it, mail him a key, and use the Filter module to decrypt at runtime using his

Re: Commercial app demo

2000-02-09 Thread Jeffrey W. Baker
Chip Turner wrote: The problem is that no matter how you encrypt the system, it has to know how to decrypt itself. That is, if you xor, or even used DES or IDEA or whatnot, the key (password, etc) has to be included with the modules, and therefore a suitably sophisticated programmer could

Re: Commercial app demo

2000-02-09 Thread Ken Williams
How about only shipping part of the software, with the remaining part of the software running on your own (not the client) machine? For instance, certain subroutines could be split off, and the input output could be passed back and forth between the client and the vendor. Then you can easily

Re: Commercial app demo

2000-02-09 Thread Fabrice Scemama
There's another way. We can't build pre-compiled modules easily, but even when you code in C or Java, desassemblers can extract some source from the binaries you deliver. As far as perl scripts are concerned, a workaround consists in trivially removing all comments and \n from the source, which

Re: Commercial app demo

2000-02-09 Thread Chip Turner
Fabrice Scemama [EMAIL PROTECTED] writes: There's another way. We can't build pre-compiled modules easily, but even when you code in C or Java, desassemblers can extract some source from the binaries you deliver. As far as perl scripts are concerned, a workaround consists in trivially

Re: Commercial app demo

2000-02-09 Thread Stas Bekman
Matt Sergeant [EMAIL PROTECTED] writes: Has anyone delivered a commericial mod_perl application before? If so, how do you handle demo versions, preferably with expiration dates? One thought is to simply xor encrypt some of the modules when the user downloads it, mail him a key, and