如何在应用程序中实施灵活的试用版本和许可选项
管理层要求我们研究在一些现有应用程序中实施许可功能。到目前为止，这些应用程序只是付费的，客户可以随意安装它们。我们需要实施新的许可模式来产生更多收入，因为我们的旧产品运行良好，人们没有理由升级。因此，我们的新客户将必须支付许可费和/或限制他们可以安装的数量。我以前从来没有处理过这些东西，所以请原谅我的无知。我需要尽可能多的指导（引导我朝正确的方向前进就太好了！）。我们需要以下...
- 限时演示版本。当他们安装该软件时，它会在固定的时间内使用全部功能。之后，当他们尝试运行它时，它会告诉他们许可证已过期。
- 限制应用程序在特定计算机上运行的许可选项。
- 限制应用程序由特定用户运行的许可选项。
- 许可选项将应用程序限制为一定的用户总数或并发用户数。
第一个很容易弄清楚，但我不知道如何去实现其他三个。非常感谢任何建议。
Management has asked us to look into implementing licensing features into some existing applications. Up to this point these apps were simply paid for and customers could install them as they please. We need to implement a new licensing model to generate more revenue because our older products work well enough that people do not have a reason to upgrade. So our new customers will have to pay licensing fees and/or be limited to how many installations they can have. I have never dealt with this stuff before, so please pardon my ignorance. I need as much guidance as possible (steering me in the right direction would be great!). We need the following...
- Time limited demo versions. When they install the software, it works with full features for a fixed amount of time. After that, when they try to run it, it tells them their license has expired.
- Licensing option that limits the app to run on a particular machine.
- Licensing option that limits the app to being run by a particular user.
- Licensing option that limits the app to a certain total number of users or concurrent users.
Number one is pretty simple to figure out, but I have no idea how to go about implementing the other three. Any advice is greatly appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我会诚实地考虑第三方解决方案。许可本质上涉及很多概念，只需花费一周的开发时间，您就可以购买功能齐全的许可产品来集成到您的东西中。在这种情况下，自己编写可能不值得这么麻烦。
我之前曾使用 Desaware 许可系统进行基于用户和机器的许可。运作良好，没有任何抱怨。我相信他们的框架足够强大，可以满足您的所有 4 个要求。 http://www.desaware.com/products/licensingsystem/index.aspx
I would look at 3rd party solutions for this honestly. There are a lot of concepts intrinsically involved in licensing, and for the cost of one week of development time you can buy a fully featured licensing product to integrate into your stuff. This is a case where writing your own is probably not worth the hassle.
I've previously used the Desaware licensing system for user and machine based licensing. Works well enough, no complaints. I believe their framework will be robust enough to handle all 4 of your requirements. http://www.desaware.com/products/licensingsystem/index.aspx
所有这些场景实施起来都可能相当复杂，但要恰到好处（而且毫无麻烦）。不要在此浪费时间，请考虑使用商业许可解决方案，例如 CryptoLicensing。它支持您想要的所有场景，包括试用、机器锁定、用户锁定和浮动/并发。
免责声明：我在 LogicNP Software 工作，该软件是 CryptoLicensing 的开发人员。
All these scnarios can be pretty complicate to implement and get just right (and hassle-free). Instead of wasting your time on this, consider using a commercial licensing solution like CryptoLicensing. It supports all the scenarios you want including trials, machine-locked, user-locked and floating/concurrent.
DISCLAIMER: I work for LogicNP Software, the developers of CryptoLicensing.