> I have *never* heard of daily activation, and I have a feeling that > it would not be well received. > But yahoo, hotmail, ebay, amazon require you to sign in, in many cases automatically each time you access your account. Its not so much activation as its verification of an account in good standing. Instead of having them authenticate certain CPUs (as Native Instruments and Waves do in the music software world), what about just surreptiously maintaining a database of all logins on the server which keeps track of their mac address or isp address. If the number of different addresses for a user exceeds 5 in any given month, then a "piracy alert" would be flagged internally. It doesn't do anything, but alerts you the developer to the possibility that someone is sharing their license. If this never happens, then no need to do much about it, and if it does happen, you do things like give them a new code and deactivate the old one.
> Unless you are already established > with a niche application (so they have to accept it) > > It might be the case that all of get used to paying for subscriptions, maintence, and more stringent copy protection. For an example, look at us with RB, most of us have bought into the "rapid release model" with little complaint - even though bug fixes do not occur until the next quarter at the soonest by which time your license may have expired so you are in essence paying for bug fixes). We have all just accepted this proposal and hope for the best with each release. > > If you are targeting Universities or Companies, a site license server > application may be the way to go. A server app like this is possible > to create in REALbasic, but would be best if you have the REALbasic > Professional version so that you can create it as a "service" which > would automatically launch when the computer is rebooted, and does > not require a user to be logged in. The concept for the server app > is almost the same as internet activation, except that you would be > using TCP or UDP sockets instead of the HTTPSocket. > > I do indeed have the professional version but I am an ignoramus regarding networks. Can you point me in a direction to learn about this? I assume the application sends and recieve messages via one of these protocals, and there must be some event change/action event that fires when a message comes in? So I would have two different apps - one of the server and one of the served computer which are set up to talk to each other. Is this right? Thanks Phil Greg _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
