From: Christian Neukirchen Date: 2005-02-05T20:14:44+09:00 Subject: Re: Ruby for closed source projects Michael Gebhart writes: > Yes, sure you are right. But one example: I wanna have a registration code > in my application. The user gets a code to activate some more features. In > the code, there only is a flag reg=true/false. When the code is entered, > the application checks it and sets the variable to true, or false. The > user can now take a look at my code and simply change this part. After the > check he sets: reg=true. > > So my mechanism to check the code is not useful. Also if I try to do the > check of the code on a external server and give back a true or false, the > user can change this part in the code directly. > > Ok, now you can say: registration codes are ugly and everything has to be > opened :) Sure, but if it is a commercial project, there is no other way. Sure there is. For example, you simply could send the customer a module which contains the advanced features instead of a registration code. As Ruby (and almost every other language) can load code at run-time, this shouldn't be a problem to implement. > Greetings > > Mike -- Christian Neukirchen http://chneukirchen.org