Thanks very much for the replies.
I had assumed that it was going to be pretty much a case of practice /
familiarisation.
Though I did find this - which is helpful for my purposes...
http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29
Gavin.
On May 10, 6:16 am, Sean Corfield
Hi there everyone.
I have been asked to think about - which is code for make happen as
soon as possible...
Implementing licensing into our application.
I have visited our good friend Mr. Google... But as you can appreciate
any search with licensing in it - doesn't quite give me what I
want
OK,
Here is some more information as requested by Mr Buzzy in another
thread;
Assume this is our layout.
http://www.positioniseverything.net/explorer/images/pict1.gif
When you click on a link in the LHS navigation bar, the main content
is updated to reflect the choice you made.
The main content
Generate a key,
A key is made up of segments normally
So for example
----
Section 1 might be a customer id
Section 2 might be a IP checksum
Section 3 might be some version etc
Etc etc
The last section is normaly a checksum of the other sections, stopping you
changing one
Similar to Dale's suggestion. We embed keys in certificates upon
completion of our e-learning courses. They comprise known things like
clientID, executionID or whatever else identifies the item and then we
just hash it. We then allow governing bodies to login and enter the
key (which appears on
So how do you check that the key is valid then?
Do you need to store valid keys in the application like a pubic /
private key pair?
Or do you simply check via the checksum, alone?
A the penny has dropped
That's why key generators are successful.
Because they create valid segments and a
Because we can hit a database and we authenticate the user they can
enter pretty much any info from the printed certificate to validate
it. We do store the hashed key for lookup.
Checksums (with my limited understanding) are probably more useful in
cases where you can't get back to check a
