I know that the specific password a user needs to unlock a protected eBook depends on some data related to the users computer. For instance, computer A will need password no 712 to unlock the ebook after download.
Question: Will the SAME computer require the SAME password number every time the SAME eBook is downloaded and started? Or does the number also depend on some non-static parameter, such as current time of first launch or such?
The reason I wonder is the situation that occurs when a user requests a refund after having purchased a password to unlock the eBook.
It is probably straightforward to use active script in a form to use for refund requests from within the eBook. And thus relock the eBook upon submission of the form. Possibly one can also remove that particular password from the list of password that may be included in the book when using some APS (automated payment solution).
But if the user will be prompted for the very same password every time, he only needs to download the eBook again after requesting said refund.
Please tell me that there is some dynamic parameter involved!
Ah, you've found the fly in the oinment. Yes, the same ebook will always require the same password whenever loaded onto the same system. There are low-lifes who purchase ebooks knowing that they are going to ask for a refund. It is a small of percentage, but charge-backs always hurt.
Fortunately GoldPanner Software offers an APS that also diables the ebook when there is a refund.
A simple alternative is to provide the refund mechanism from inside the ebook. If they use the refund form within, it also closes the ebook for good, and leaves a cookie that says so. A cryptic, hard-to-find cookie. A cookie the ebook looks for upon startup.
The other 'expedient' method (read 'cheap, and maybe 'lazy') would be to keep a list of ID's that have asked for a refund (assuming that this list would not get too long), and add a simple check-in script on your server to see that this ebook has never been refunded for that ID.
The internal refund method is how HYPrLocks 2 works. The advantage (for none programmers) is that it also has an Automatic Payment System where the customer is immediately given the code to unlock the ebook.
Storyman: I realize that though it would be simple for AEC/Sunil to check not only motherboard, but also randomize it with time-of-intitial -load (like the second its first launched or so), it might not be desiarable anyway.
Ordinary users who misplace their code, and must reinstall after a crash would need a new password as well...
Alaska: do you mean that cookies set by the ebook go under the radar of "delete cookies" from within browsers? that also leads onto this other thread, perhaps you can please chime in there as well:
I was typing/thinking 'on-the-fly', as well. ...better yet would be to provide a registry setting. I am preoccupied with web issues, so I was thinking cookies.
A registry setting could be deleted as well, but it would be a bit more difficult for the average user.
With any business, it is up to the individual owner of said business to ensure the success of the business. You may make more or less than any sample figures or results that might be quoted on our web sites or other publications. All business involves risk, and many businesses do not succeed. Further, Answers 2000 Limited does NOT represent that any particular individual or business is typical, or that any results or experiences achieved by any particular individual/business is necessarily typical.
