validating "per use" licensing

[Peter Haworth]

Try ZygoDact, it already does all this for you. www.hyperactivesoftware.com
Pete
lcSQL Software <http://www.lcsql.com>



On Thu, Jul 12, 2012 at 10:34 AM, Dr. Hawkins <dochawk at gmail.com> wrote:

> I want people to be able to pay "per use" for the product.  In this case,
> it would mean per client file.
>
> My thinking is that I embed a large random string in the source code of
> their copy, and keep a copy of the string myself.  When a license is
> purchased, it would be for a particular last name and last four digits of
> that client's social security number.  Upon payment, my server would run a
> hash on the random string, the name of my customer, and the client info
> from their customer, and produce a key.  At the client end, this key is put
> in a list.  When the program runs, it would run the hash, and if the key
> exists, it could proceed.
>
> Is this a sensible approach?  And and any suggestions on the hash to use?
>
>
> --
> The Hawkins Law Firm
> Richard E. Hawkins, Esq.
> (702) 508-8462
> HawkinsLawFirm at gmail.com
> 3025 S. Maryland Parkway
> Suite A
> Las Vegas, NV  89109
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>