> I'd recommend that you use the "RegCode" format if you want to sell your
> program online through PGHQ or PalmCentral. See:
> http://www.palmcreations.com/regcode
> There is src and example code there.
Jason,
As a shareware developer, I'm keen to find something that takes me out of
the sales loop ... but I think RegCode is the wrong solution for the
following reasons:
1. Each user already has an id, why complicate matters by inventing a
second?
2. The HotSync id is common to all applications (and can be stored in the
seller's database) whereas, if I choose it, a RegCode may be unique.
3. It's unreasonable to ask a user to type in a string of (up to) 22 hex
digits plus colons.
4. The hex string doesn't "scan" well whereas the HotSync id (likely based
on the user's name) does.
5. The resultant unlock code of 5 digits is too short and can easily be
cracked by some automated routine.
6. I want to store more info in the unlock code, e.g. registration date,
product code.
The solution I've used over many years with reasonable success is to be
loose when dealing with the input key (in this case the user's HotSync id).
For example (without being too specific) ignore case, spaces and
punctuation, high-ASCII etc. The code I generate uses digits only, looks
like a credit card number and you can be loose when parsing the code as
well. If you're smart, you can probably work out if the code entered is a
typo or belongs to someone else.
Stephen Best
Bitware Australia Pty. Ltd.
