LiptonFor a client with a somewhat complex setup of virtual machines I would like to know whether the storage location of the server info (set via TF_SaveServer) is secret or not.It would be interesting to know where it is stored. They particularly would like to know whether it is stored as part of a user profile.
Thanks in advance - we love the product!
It's not secret, but it's an implementation detail (meaning it has changed, and will change). If you use TA_USER then it's stored in user specific folders. If TA_SYSTEM is used, then it's stored in system specific folders.
Other than that, don't depend on implementation details or things will break.
LiptonThanks, Wyatt!
We use TA_USER. Can you share the location for TA_USER in the latest version of TurboFloat?
No. Don't depend on the location. It has changed and will change.
LiptonOkay, correct if I'm wrong, but this seems not to be a perfect solution yet.
1. If a client works with virtual machines, it is highly recommended to use TurboFloat because the concept of hardware locking fails on VMs.
2. However, in environments with employees working with clean virtual machines that have their user data loaded and stored with each session, TF_SaveServer is pretty much pointless because the storage location of server info is out control.
>> "2. However, in environments with employees working with clean virtual machines that have their user data loaded and stored with each session, TF_SaveServer is pretty much pointless because the storage location of server info is out control."
Yes, if the VMs are wiped on every launch (which is very user-specific -- not the use-case for most customers).
So, yes, for this use-case you'll need to call TF_SaveServer() on every launch.
But verify this is actually happening in reality before spending time solving a problem that may not even exist.
