I have questions regarding the behaviors of LexActivator and LexFloatClient.
LexActivator offers the use of the SetActivationMetadata() and GetActivationMetadata(). We plan on using these to keep track of the number of times that applications are started, the total execution time, etc. Does LexFloatClient() offer such a mechanism?
Some routines from LexActivator and LexFloatClient feature the same names, which creates conflicts when linking with both libraries. This gives us the impression that we are not expected to try creating an application that links with both libraries simultaneously. Are problems/pitfalls to be expected? If so, what should we do to support both hosted and local license servers from the same application?
The hosted server offers an interface to monitor and delete activations. Is a similar interface available with LexFloatServer? If an application crashes without releasing it’s license, is expiration the only recovery mechanism?