I haven't been able to find much reading material on this but it is the most important part of protecting or commercially releasing custom indicators or EAs.
I have purchased a hosting plan which allows me to put up some MySQL databases but I can't find any documentation on different methods to protect my work when I do something for someone and don't want it being mass distributed because I still intend to keep the software's intellectual property.
There seems to be two popular ways to protect software out there and I would like to read up on both if I could find the material.
Method 1: Have a user specific code in the database that must be entered into the indicator/ea options upon attaching it to the chart and this is verified by having the indicator/ea connect to the database and verify authenticity. The problem I see with this is how to ensure the code is only being used by that one person and not shared (would have to log IPs that are using the code etc).
Method 2: Have the user provide their account number they intend to use the EA/Indicator with and have that in the database which the program would then authenticate. Problem here is what about for people who want to use it on demo accounts, can the program figure out whether or not to authenticate based on the account number (do I know if it's a demo or live account from the account number)?
Anyone have any reading material that covers this, any books or online tutorials that cover it?
Thanks all!
I have purchased a hosting plan which allows me to put up some MySQL databases but I can't find any documentation on different methods to protect my work when I do something for someone and don't want it being mass distributed because I still intend to keep the software's intellectual property.
There seems to be two popular ways to protect software out there and I would like to read up on both if I could find the material.
Method 1: Have a user specific code in the database that must be entered into the indicator/ea options upon attaching it to the chart and this is verified by having the indicator/ea connect to the database and verify authenticity. The problem I see with this is how to ensure the code is only being used by that one person and not shared (would have to log IPs that are using the code etc).
Method 2: Have the user provide their account number they intend to use the EA/Indicator with and have that in the database which the program would then authenticate. Problem here is what about for people who want to use it on demo accounts, can the program figure out whether or not to authenticate based on the account number (do I know if it's a demo or live account from the account number)?
Anyone have any reading material that covers this, any books or online tutorials that cover it?
Thanks all!