I am considering applying server-side licensing for my javerScript application.
In the document below, there is a phrase “Our server-side licensing component is written in C++.”
(https://support.scichart.com/support/solutions/articles/101000515345-scichart-js-domain-licensing-faq)
However, there is only asp.net sample code on the provided github.
(https://github.com/ABTSoftware/SciChart.JS.Examples/tree/master/Sandbox/demo-dotnet-server-licensing)
I wonder if there is a sample code implemented in C++ for server-side licensing.
Can you provide c++ sample code?
Also, are there any examples to run on Ubuntu?
- brad leppert asked 1 year ago
- last edited 2 months ago
Hi Brad, we’ve never heard of Tauri, but I’m sure we can make it work. How about if you submit a boilerplate like our Electron app, we can look at the licensing. Electron is license simply by AppID so hopefully there’s something similar in this framework. If not we have a mechanism called “Server Side Licensing” which allows you to license any app via a RPC call as you described. Thanks for considering SciChart!
I finally got an example put together that works with a trial key and displays a basic plot (Update #2 in my post). Per David’s answer, it seems like Tauri is not using file://, but instead a custom asset:// protocol.
- You must login to post comments
Hi
I was able to build and run your tauri example on Windows, and generate a runtime key that works for it. No serverside awkwardness required.
We look forward to seeing what you can do with tauri and SciChart. I would be interested to know what the story is for moving data from the server side to the webview, particularly whether you can pass data as binary, or whether everything has to be serialised to strings as in electron.
Regards
David
- David Burleigh answered 1 year ago
- You must login to post comments
Hi
The key issue will be the way the html is loaded into the webview within a tauri application. Normally in electron the html is loaded using file://, which means it does not have a domain, hence we restrict on applicationId, which as you say would be productName in tauri. If it is loaded with some other protocol such that the page appears to have a domain, then a domain license would be required.
Storing the actual key in the back end and then fetching and applying it in the front end as you show is definitely the way to go.
Give it a try with a trial key, and once you have a minimal working example, send it to us and we can check the runtime key behaviour.
Regards
David
- David Burleigh answered 1 year ago
- You must login to post comments
Please login first to submit.
