Support Board
Date/Time: Thu, 31 Oct 2024 10:12:34 +0000
Post From: Protecting studycollection with an 'expiration date'
| [2024-09-08 17:50:24] |
| ondafringe - Posts: 281 |
|
If I needed to create/distribute an ACSIL custom study, and I was *serious* about treating this like a business, and I wanted to retain *complete* control over every aspect, especially the ability to grant/restrict access, using Visual Studio, I think I would: 1. Create a single, ACSIL custom study that includes everything I wanted to protect (and C++ is harder to reverse engineer) 2. Make certain my custom study was created in a way that prevents memory conflicts should the study be loaded on multiple charts 3. Create a C# Minimal Web API that uses some flavor of SQL as a database 4. Create a number of SQL stored procedures to perform relevant tasks on the database 5. Add Authentication/Authorization to the API 6. Register a domain name, find a domain/SQL host, and deploy my API to that host 7. Add code to my custom study that runs in the background to get the user's account number, and access my API's endpoints 8. Create a C# Windows app -- for my use only -- to access my API in order to perform admin tasks on the database As far as distribution: I would create an email address with an auto-responder. If someone sends an email to that address, the auto-responder would send them instructions on how to use the custom study... and it would either send them a copy of the study as an attachment, or include a link where the study could be downloaded. Once I had all that, my custom study would automatically add new users to the database... allow free trials... check for access permission. And using my admin app, I could grant/restrict access for one, multiple, or all users... force users to download and use a new version... check for payment... and who knows what else. And since one study/same code works for all users, it wouldn't matter if users passed my study around to anyone or everyone. In fact, passing the study around to other users would simply add one more distribution channel. But, hey, that's just the way I would do it! lol Date Time Of Last Edit: 2024-09-08 18:11:56
|