Trevor G Quayle wrote:
> Fa3ien <fab### [at] yourshoesskynetbe> wrote:
>> Since POV-Ray (for Windows, at least, I don't know about other systems)
>> is already able to access the internet to give some feedback or check
>> for updates, why not :
>> - set an expiration date in the binary
>> - once the expiration date is over, if there is no new beta,
>>    POV-Ray can get some kind of "certificate" which allows it
>>    to continue working as long as the Team wishes.
>>
>> (of course, this has problems like "not every machine running
>>   POV-Ray has internet access", etc.. but it might be a nice
>>   solution for most people)
>>
>> It could also take the form of some "licence file".
>>
>> Fabien.
> 
> Or built-in unlock codes that are only released by the team when necessary.
> (beta expires with no new one available)
> 
My suggestion still is to compile a few beta's with different expiry 
dates and release an extended beta when necessary. That costs a 
recompile but there is no change of the current code required.

Post a reply to this message