wyDay blog  |  Downloads  |  Buy
LimeLM
wyBuild
Support forum
wyDay blog
wyDay Home

The wyDay blog is where you find all the latest news and tips about our existing products and new products to come.

wyDay blog

Posts in the ‘LimeLM’ tag

Today we've released TurboActivate and TurboFloat 4.4. These releases bring a number of improvements (security, build size, speed) and a few new features.

m1-chip.jpgThe biggest new feature is support for Apple's new macOS platform: ARM64. Or, as they like to re-brand everything in their own image: "Apple Silicon". TurboActivate, TurboFloat, and the TurboFloat Server all have "universal builds" that support Intel 64-bit macOS and ARM64 macOS.

We've also dropped support for old FreeBSD versions because the FreeBSD team doesn't have the resources to properly test more than one version. So, from now on we'll only release builds for the latest version. As of this blog post that means just FreeBSD builds for 12.2.

If you haven't already signed up for the best software licensing product, then sign up for LimeLM right now! We support all major operating systems (Windows, macOS, Linux, BSD) and we have articles and examples for all popular programming languages.

Tags: LimeLM

Today we've released TurboFloat 4.3. The marquee feature of this release is that when your app uses the TurboFloat library your app can now release any active leases when a computer goes to sleep. And your app will also attempt to regain that lease when the computer "wakes up".

An example of a computer going to sleep is when your customer shuts their laptop:

close-laptop-1.gif

The laptop is now asleep. If you were using TurboFloat in your app, and your app had a lease before the computer went to sleep, the lease would be dropped immediately. This frees up the lease to be used by any of that person's colleagues.

Humans are messy and unpredictable

This feature is just the latest example of our focus on real-world user-behavior. A customer isn't going to switch to every app they have open, see if it's using floating licensing, and if so, invoke whatever method you've created to drop the lease while keeping the app running.

That would be a nightmare; no one has time for that.

A real person is either going to just walk away from the computer (and the computer will put itself to sleep after a few minutes). Or the person will explicitly put the computer to sleep (for example by shutting the laptop).

Our job is handling this, and other real-world behavior, so you don't have to.

If you're not already using TurboFloat for your floating licensing, signup for LimeLM today (it's free to try — no credit card needed).

close-laptop-3.gif

lease-issue.gifWe're proud to announce that we've made it possible to sell your app on a per-process-instance basis. Meaning you can directly limit how many instances of your app your customers can run at any one time.

It's available now for all LimeLM customers!

This new per-instance lease issuance is the alternative to the per-user-session leases that TurboFloat Server issued by default. The differences between the two is shown in the gif above as well as described in "Fine-grained control: per-instance vs. per-user session leases":

With the release of TurboFloat 4.1 we added the ability to issue leases either on a per-process-instance basis or a per-user session basis. This gives you more control over how you sell your software and how it's used by your customers.

For per-user-session leases, one lease is issued per-user session on a machine (real or virtual) that is using at least one instance of your app. For example, "Sally Doe" starting your app on a shared server will be able to start multiple instances of your app and it will use that one lease regardless of how many instances they start in that user-session on that machine.

For per-process-instance leases, one lease is issued for every instance of your app started. Every separate process-instance of your app started will request a license lease whether the separate instances are in the same user-session or are in multiple different user-sessions.

So, how do you use it? Simple: first, make sure you're using the latest version of the TurboFloat Server and TurboFloat library (get them on your API page). Then create a new TurboFloat Server key (or edit an existing one) and select the "per-process-instance leases" option.

That's it. We handle the rest. Easy-peasy, lemon (lime?) squeezy.