TurboActivate and TurboFloat support in a single product (yes, it's possible)Solved

Hi Wyatt,

We have a product supporting TurboActivate and its running successfully.

However, we wanted to add TurboFloat services too.Is it possible to implement both services for a product.We can add an option to choose between the two services at the time of installation.

Your thoughts?

>> "Is it possible to implement both services for a product."

Yes, we have a number of customers doing it.

How you give your customers a choice is up to you. We recommend forcing all users on virtual machines to use TurboFloat. And for all customers give the user a choice.

Ultimately, though, it's up to you.

Thanks for the reply Wyatt!

I was going through the documentation for TurboFloat and encountered this :https://wyday.com/licensechest/help/create-tfs-instance/

Is this feature coming soon?

>> "Is this feature coming soon?"

Yes.

Hi Wyatt,

Is there any update on the cloud turbofloat instances? Your docs about turbofloat (which we link customers to!) currently recommend to customers a non-existent solution which is not ideal. A hosted solution will be great - is this weeks/months or years away?

https://wyday.com/limelm/help/turbofloat-server/

Our hosted solution is weeks away.

And you also have the options of hosting the TFS instance on the customer's infrastructure or hosting it on your infrastructure.

We released TA, TF, TFS 4.1.x first so that our customers could get the benefits of our many months of work without having to wait for everything to come out at once.

Is this ever coming? we're now more than 2 years down the road since first mention that it was coming very soon...

Yes, it's coming. No hard date. ASAP.

As you can see we've made several visible releases since we first started publicly talking about LicenseChest. Not to mention "invisible releases" (backend improvements, addressing security proactively, etc., etc., etc.).

As had been said ad-nauseam: we do not release roadmaps. And until we've implemented time-tracking into our back-end processes we do not give release dates any longer. Any hint at a time-frame you get from us is just a guess based on current work-loads, internal roadmaps, employee performance, etc., etc.

When things change internally, we do not go back and edit posts, contact people, etc. Any guesses are guesses based on a snapshot in time.

Long story short: it'll be out when it's out. We want it out as much as our customers do.

Reply
Discard post