TurboFloat- limiting instances on same computer

This is in a Windows 7 environment and using C# as the main operating language.

I am running the TurboFloatServer.exe directly from the command-line for testing purposes.

I started up the TurboFloatServer, and then ran my program. The program correctly registered a floating license with TurboFloatServer, etc. Then, without closing the program, I started up a separate instance of the same program. This separate instance did not request a separate floating license, but appeared to use the same floating license as the other instance. Is this behavior by-design? Would we have the same behavior if each instance was started under a different user?

If this is by-design, then if a user decides they want to start multiple instances of my product on the same computer (logged in as the same user), then I have to keep track of the instances that are open in order to determine when to release the lease. Otherwise, the user could lose their lease just through closing one of the instances of the program, etc.

But as a larger problem, some of my clients intend to use this program with Citrix XenApp so that they don't have to install the program directly on the user's computers. I am concerned that if they use session virtualization (ie, our program actually is running on a server, but the users interact with it from their computer), then all the instances of the program will run on the same computer. Would then TurboFloat see all the instances as being associated with the same lease since they are running on the same computer? I guess I'm not familiar enough with XenApp to know if the session virtualization would log the user into the server as a different user or the same user.

This separate instance did not request a separate floating license, but appeared to use the same floating license as the other instance. Is this behavior by-design?

Yes. Although we will be adding a feature in the following months that will allow you to specify that each instance (even if they're instances within the same session) is forced to get its own license lease. But for most users we wouldn't recommend that behavior.

Would we have the same behavior if each instance was started under a different user?

No, separate sessions on the same computer would each get their own license lease.

Otherwise, the user could lose their lease just through closing one of the instances of the program, etc.

Yes, currently. We're making this better in the near future (that is, TurboFloat will handle it internally so that this doesn't happen). Most customers get around this by making their app single-instance within the session. But we know not all apps are like that.

Would then TurboFloat see all the instances as being associated with the same lease since they are running on the same computer?

No, TurboFloat was specifically designed to handle cases like this. Your app would run under separate sessions, and thus get separate leases for each session (even if the Citrix server is on 1 physical machine).

Does that make sense?

That does make sense- sounds good. Thanks!

Reply
Discard post