From: Peter Krueger (pkrueger++at++appss.de)
Date: 03/26/2004 05:44:22
Daniela Rainer <dr++at++vircinity.com> wrote:
> our application crashes in pfInit under Linux with Performer 3.1
> if it is linked with flexlm (for our own licensing).
>
> In Performer 3.0 we had a similar problem, but found a workaround:
> we could not checkout a Performer license, if linked with flexlm.
> The workaround was, to checkout the license inside a shared library,
> that does not export all symbol inherited by flexlm. This
> workaround doesn't help any more.
>
> Any help from performer or flexlm experts would be appreciated.
Hello Daniela,
if you still have problems with flexlm, I can offer you an alternative.
Our company has developed an own very powerful and flexible license
manager, the "appss License Manager". It's main advantages are:
- Flexible management of licenses in a license pool. If a customer wants
to use the licensed software in a pool of say 5 computers, but he buys
only two licenses, the software can be used on all 5 computers, but not
more than 2 copies of the software can be run simultaneously.
- All-purpose license manager: The license manager can handle
simultaneously licenses for different software products, even if they
come from different vendors (as long as all vendors use the appss
License Manager). Every vendor can only generate licenses for its own
products.
- Fail-safe implementation: The software can get its license from a remote
computer in the license pool. In case of a crash of the remote computer
the software silently tries to get another license from another computer
in the pool. If a license on the local computer is available, this
license is used first to minimize the risk of a license loss.
- Operating system independence: The license manager works on Windows,
Linux, and Irix. It is fully compatible for these systems. A licensed
software running on one operating system is able to use a license from
any computer in its license pool, regardless which operating system is
used on the other computer.
- Password protection: The computer that provides licenses can
protect them with lists of passwords. This enables companies who
purchased a large amount of licenses to share them temporarily with
external project partners. After the project is completed a simple
change of the password disables the external partners (who didn't buy
the licenses themselves) from using the licenses further on. So they
can't "steal" the licenses from its owner against his will.
- Feature control: A license can contain application specific data which
can be used to enable or disable some features of the application. This
allows you to create e.g. "basic", "professional", and "premium"
versions of your software which are all the same executable. The license
determines at runtime how many features your software offers to the
user.
- Ability to update licenses: A customer may first buy a "basic" license
and decide later, that he needs more features. You can offer him a
"professional" license for an update price if you like. The new (more
valuable) license automatically disables the older one (as long as
both licenses belong to the same computer).
- Validity limitation: A license can be limited in its validity (but it
doesn't have to). This allows e.g. the generation of 30-day-evaluation
licenses.
- Language bindings: The license manager can be used with C++ projects, a
Java binding is currently in progress.
If you're interested in more information feel free to contact me.
Best Regards,
Peter
-- ==================================================================== Peter Krügerapplied software solutions (appss) GmbH Sandtorstr. 23 D-39106 Magdeburg Germany
Phone: +49-(0)391-54486-19388 Fax: +49-(0)391-54486-19222 email: krueger++at++appss.de URL: http://www.appss.de
Managing Director: Uwe Hess, Dietmar Schäfer Register: HRB12386, AG Mageburg
"Virtual business becomes reality!"
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden. ====================================================================
This archive was generated by hypermail 2b29 : Fri Mar 26 2004 - 05:48:02 PST