Custom Field for poll

Hey Mike,

Yes, but it would involve an extra step (you'd need to call TA_IsActivated() first, get the values, pass them to TA_IsGenuineEx()), and it needlessly complicates your code.

What is the problem you're trying to solve. It's likely there's a better solution.

Hi Wyatt,

The problem I am trying to solve is for some users we may want to set the poll to 90 and grace time to 10000 days (essentially never expire their license if they're offline, since they may not have a net connection at all after initial activation). For other users we could do the 90 days poll and 14 days grace. We want to use the same build for both type of users. There may be other poll intervals / grace period days that we may want.

By having the poll interval and grace period configurable through licensing, we do not have to make separate builds for each of the different settings.

- Mike

Hey Mike,

Just have customers that need to use your app offline (for whatever reason) activate offline. And then be sure to use a the "TA_SKIP_OFFLINE" flag in TA_IsGenuineEx().

So customers that activate offline can continue to use your app even after the nDaysBetweenChecks and GracePeriod.

Hi Wyatt,

If the user activated the product key online and the TA_IsGenuineEx is called with the TA_SKIP_OFFLINE, and the user stays offline will the future TA_IsGenuineEx (with TA_SKIP_OFFLINE) calls return the license is invalid after the poll+grace interval?

Thanks,

- Mike

No, TA_SKIP_OFFLINE only works if they customer activated offline.

The good news is that if a customer activated online originally, and then wants to continue offline they can then activate again offline and it will use the "same slot" in LimeLM and TA_SKIP_OFFLINE will work for the customer.

Wyatt wrote:> Just have customers that need to use your app offline (for whatever reason)> activate offline. And then be sure to use a the "TA_SKIP_OFFLINE"> flag in TA_IsGenuineEx().> > So customers that activate offline can continue to use your app even after> the nDaysBetweenChecks and GracePeriod.

Is there an equivalent to T_SKIP_OFFLINE for TurboFloat, too? Seems like that would have to be set up in the TurboFloatServer-config.xml which would mean that customers would be able to enable this themselves...

Wouldn't it make sense to make this (i.e. the ability to remain offline permanently) a property of the license itself (similar to the "Allow VM activations" setting) rather than a flag on IsGenuineEx()?

Cheers,

Oliver

No, TurboFloat is designed to contact the TurboFloatServer at an interval. If a customer needs to run TurboFloat on a locked-down network they can. And they can even activate the TurboFloat Server offline.

OK, but isn't the TurboFloatServer trying to contact the wyday.com activation server at 90 day intervals (or whatever is specified in TurboFloatServer-config.xml), too? Or are you saying that it implicitly wouldn't as soon as the server was activated offline? If so, I wasn't yet aware of that implication... (but it would probably solve the scenario I'm currently dealing with)I would have expected to have to repeat the offline activation process every 90 days (which both I and the customer obviously wouldn't have wanted to do).

Cheers,Oliver

The TurboFloat Library only ever contacts the TurboFloat Server (whoever that particular customer has chosen to host it).

The TurboFloatServer, when activated offline originally, will try to contact the LimeLM servers at the interval set, but it wont stop running if it fails to reach the servers within the grace period.

Wyatt wrote:> The TurboFloatServer, when activated offline originally, will try to> contact the LimeLM servers at the interval set, but it wont stop running> if it fails to reach the servers within the grace period.

OK, and it will not only continue running but also continue to serve valid leases, right? And I assume this will also continue to be the case beyond the grace period? Or would the offline activation process indeed have to be repeated every 104 (90+14) days after all (I'm only asking because you qualified your statement with "within the grace period")?

RFE: Again, I think it would be great if in the future "Allow permanent offline activation" could simply be a property of the individual key (for both TA and TF) analogous to "Allow VM activations" rather than something that either has to be implemented by hand (for TA via TA_SKIP_OFFLINE) or that simply happens implicitly (for TFS - if I understood you correctly).

Cheers,Oliver

>> "And I assume this will also continue to be the case beyond the grace period?"

Yes.

>> "RFE: Again, I think it would be great if in the future "Allow permanent offline activation" could simply be a property of the individual key (for both TA and TF) analogous to "Allow VM activations" rather than something that either has to be implemented by hand (for TA via TA_SKIP_OFFLINE) or that simply happens implicitly (for TFS - if I understood you correctly)."

The use-case for something like that would be extremely limited. And is already solved by having customers that can't activate online, instead activate offline (thus solving the problem).

Of course it requires your app to have the correct flags set, but that's a solvable problem on your end. (Our default examples for every language show setting the TA_SKIP_OFFLINE flag)