TA 3.3

When I asked previously about improvements coming in TA3.3 you advised that improved licence Revocation was coming. You said the TA3.3 would automate the revocation checks and only do the check every now and again (not every time the app starts)

How is this implemented in TA3.3? Currently we just deploy the TA .dat file, So how should we perform revocation with the Dat file? Or do we need to chjnage the way our app works and use your new TA EXE?

Any clarification would be appeciatedSteve

Hey Steve,

You said the TA3.3 would automate the revocation checks and only do the check every now and again (not every time the app starts)

Yes, that's included in TurboActivate 3.3. IsGenuineEx() is the function that you want to use. If you tell me what programming language you're using then point you how to use the new function. Also, note we've updated all the example code and articles to use the new IsGenuineEx() function. See: Using TurboActivate.

So how should we perform revocation with the Dat file?

The dat file isn't the license file. It's a "product details" file. (Basically it's information TurboActivate needs to know in order to activate your software).

Just use IsGenuineEx() how we recommend to and everything will "just work".

the grace period of 14 days means that the application will call the servers everyday for 14 days and if after 14days still fails to connect then it deactivates, or that it tries/calls just one time after 14 days ?

the grace period of 14 days means that the application will call the servers everyday for 14 days and if after 14days still fails to connect then it deactivates,

Yes. It's every 5 hours, but yes. If your app is only run once a day then it's every day.

Reply
Discard post