- Revenera Community
- :
- FlexNet Embedded
- :
- FlexNet Embedded Forum
- :
- Re: What is the difference "flexnet_client" and the "flexnet_client xt-c" (Flc vs Flx)
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
We've been using FlexNet Embedded for a while. We been downloading the "XT-C" version of it. Something like this
flexnet_client-xt-c-x64_windows-2020.07.0
And the APIs we call all start with the prefix "Flc".
But recently inadvertently downloaded the non-XT client. Something like this:
flexnet_client-x64_windows-2020.07.0
I thought it was the same thing. It seems to have the same samples and all that but the APIs all start with the prefix "Flx"
What is the difference between the two. Why use one of the other?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hello @jmoleary
Below is an overview of the FlexNet Embedded portfolio. And attached are two architecture diagrams of the Device Kit (Flx) and the XT Kit (Flc).
Porting Kit
Platform agnostic (C code) implementation with no dependency on the underlying operating system or runtime environment. Developed for hardware manufacturers and intelligent device manufacturers with strenuous system constraints like disk storage space, memory, no clock, etc.. Provided as obfuscated source code.
Device Kit
Tailored SDK offerings of the Porting Kit for a variety of platform (processor and operating system) combinations like Linux Arm32, HP-UX PARISC 64, etc.. Provided as pre-built or obfuscated source SDK variations of the Porting Kit.
XT Kit
Framework built around the Porting Kit for commonly used distributed desktop environments, the addition of high-level language interface support (C++, C# and Java), and deeper platform integration including security mechanisms such as tamper resistance and secure anchoring. Provided as pre-built SDKs for Windows 32/64, Linux 32/64 and Mac OS X.
CMAPI
Transition from native or SDK-driven licensing to a holistic or RESTful interface supporting SaaS and Web Application providers. Provided as secure REST API endpoints that can be consumed from either a FlexNet Embedded Local License Server and/or Cloud Licensing Service (module of FlexNet Operations).
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hello @jmoleary
Below is an overview of the FlexNet Embedded portfolio. And attached are two architecture diagrams of the Device Kit (Flx) and the XT Kit (Flc).
Porting Kit
Platform agnostic (C code) implementation with no dependency on the underlying operating system or runtime environment. Developed for hardware manufacturers and intelligent device manufacturers with strenuous system constraints like disk storage space, memory, no clock, etc.. Provided as obfuscated source code.
Device Kit
Tailored SDK offerings of the Porting Kit for a variety of platform (processor and operating system) combinations like Linux Arm32, HP-UX PARISC 64, etc.. Provided as pre-built or obfuscated source SDK variations of the Porting Kit.
XT Kit
Framework built around the Porting Kit for commonly used distributed desktop environments, the addition of high-level language interface support (C++, C# and Java), and deeper platform integration including security mechanisms such as tamper resistance and secure anchoring. Provided as pre-built SDKs for Windows 32/64, Linux 32/64 and Mac OS X.
CMAPI
Transition from native or SDK-driven licensing to a holistic or RESTful interface supporting SaaS and Web Application providers. Provided as secure REST API endpoints that can be consumed from either a FlexNet Embedded Local License Server and/or Cloud Licensing Service (module of FlexNet Operations).