My Feature request is found below.
First some background information:
We are looking to implement Hosted Floating licenses for a big US corporation.
Now, this basically works straight out of the box.
But we have concerns regarding some use cases:
What if the client has No-Internet access for a while?
*) All new tries to claim a license will then fail.
*) And all tries to release a license will fail as well… leaving many Zombie-licenses.
It’s quite a risk for a High-Demanding environment.
Is there anything else besides increasing the leaseDuration?
We would prefer it if there would be a grace period that will help them out and still allow them to use the software.
It’s just like the grace-period solution that currently comes with subscription licenses when the client is not connected to the internet.
Another concern is the way the floating licenses are released.
See Activation flow for hosted-floating licenses?
Calling DeactivateLicense () removes all the license data.
That behavior looks bad for two reasons:
- The license key is not stored by Cryptlex. A restart of the application needs a license key. Which means we need to store the license key ourselves… Which is kind of a bummer.
- This pretty much prevents the option to include a grace period — because all the license information is gone from that system.
Why not implement an alternative for the DeactivateLicense() method for hosted floating licenses?
One that keeps licensing information on that system.
So an application restart will automatically try to re-connect the license.
By doing that, it can also have a way to handle Network failures more gracefully.
How about that?