Leigh J. Halliwell wrote: > I'm building an application that runs J scripts. Is there some way by which > I can regulate how/when it will be run? For example, suppose that I sell it > to a client with a one year license. Can I build a key either into the > scripts or into J itself so that after a year it requires relicensing (like > Setinit in SAS)? I realize that I could put tests into the scripts, but a > clever user could remove them. So maybe my request calls for "invisible" > coding, i.e., encrypting the scripts. Is this possible? Thanks.
You can encrypt scripts using 3!:6. As well as your application script, you could have another encrypted file that contained your licensing information, e.g. expiry date, user names etc. When your application runs it checks the license script to ensure that it is valid. Each year you provide an updated license file to the client. There are obvious variations on this. For example, the client could control access to the app by password protected access to the license file. ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
