一般情况下要谨慎这样做。 仅在安装或首次启动产品时说明。 频率是否更高取决于 BA 对海盗的偏执程度。
Generally do so sparingly. Say only on install or first launch of the product. Any more frequency then that is determined by how paranoid the BA is of pirates.
I use a sliding window of 30 to 90 days. And the application saves the result of the license server so it will function offline. If the saved license is invalid for any reason, the server is contacted and the saved license is updated.
The application also informs the user (not with a nag dialog, dialogs are evil!) that their license will expire soon when they have less than 31 days before it expires. This is important so they don't get caught unaware of their license expiring.
As to how well this works, ask me in 9 months when our 12 month licenses expire!
The frequency with which the licensing client calls home should be configurable per licence. The reason for this is that customers differ, & you should be able to easily tailor your solution to suit.
In some cases it might be alright to hit the server every time the app starts, but some customers (e.g. most financial institutions) might prefer that you never call out but just verify the licence.
Also, the licensing API you use should provide sufficient information to know whether the check failed because it couldn't see the server, or because the licence was invalid, expired or used up (in the case of multi-seat licences).
There are several reasons for this:
The user may have installed the software on a notebook which is not always connected to the Internet.
If your company should experience licence server downtime, you don't want to prevent existing installations of your software from running.
Obligatory disclaimer & plug: the company I co-founded produces the OffByZero Cobalt licensing solution. With it, you can configure how frequently each individual licence calls home, and create offline licences that never call home. It also returns detailed information about connectivity, meaning that you can allow your application run even if the licence server is temporarily unavailable.
发布评论
评论（4）
检查应该相对较快，因此大多数应用程序在应用程序启动时执行此操作，也可以选择在日翻转时执行此操作（对于长时间运行的应用程序）
The check should be relatively quick, so most apps do it on application startup and optionally on day-rollover (for long running apps)
一般情况下要谨慎这样做。 仅在安装或首次启动产品时说明。 频率是否更高取决于 BA 对海盗的偏执程度。
Generally do so sparingly. Say only on install or first launch of the product. Any more frequency then that is determined by how paranoid the BA is of pirates.
我使用 30 到 90 天的滑动窗口。 并且应用程序保存许可证服务器的结果，以便它可以离线运行。 如果保存的许可证由于任何原因无效，则会联系服务器并更新保存的许可证。
该应用程序还会通知用户（不是通过唠叨对话框，对话框是邪恶的！）他们的许可证将在距离到期前不到 31 天的时间内到期。 这很重要，这样他们就不会不知道自己的许可证即将过期。
至于它的效果如何，请在 9 个月后询问我，当我们的 12 个月许可证到期时！
I use a sliding window of 30 to 90 days. And the application saves the result of the license server so it will function offline. If the saved license is invalid for any reason, the server is contacted and the saved license is updated.
The application also informs the user (not with a nag dialog, dialogs are evil!) that their license will expire soon when they have less than 31 days before it expires. This is important so they don't get caught unaware of their license expiring.
As to how well this works, ask me in 9 months when our 12 month licenses expire!
许可客户端打电话回家的频率应该可以根据许可证进行配置。 其原因是客户不同，& 您应该能够轻松地定制您的解决方案以适应。
在某些情况下，每次应用程序启动时访问服务器可能没问题，但某些客户（例如大多数金融机构）可能更喜欢您从不调用，而只是验证许可证。
此外，您使用的许可 API 应提供足够的信息，以了解检查失败是否是因为看不到服务器，或者是因为许可证无效、过期或用完（在多席位许可证的情况下）。
造成这种情况的原因有多种：
用户可能在并不总是连接到 Internet 的笔记本电脑上安装了该软件。
如果您的公司遇到许可证服务器停机，您不想阻止软件的现有安装运行。
如果您的公司遇到许可证服务器停机
强制性免责声明和 插件：我共同创立的公司生产 OffByZero Cobalt 许可解决方案。 使用它，您可以配置每个许可证回拨的频率，并创建从不回拨的离线许可证。 它还返回有关连接的详细信息，这意味着即使许可证服务器暂时不可用，您也可以允许应用程序运行。
The frequency with which the licensing client calls home should be configurable per licence. The reason for this is that customers differ, & you should be able to easily tailor your solution to suit.
In some cases it might be alright to hit the server every time the app starts, but some customers (e.g. most financial institutions) might prefer that you never call out but just verify the licence.
Also, the licensing API you use should provide sufficient information to know whether the check failed because it couldn't see the server, or because the licence was invalid, expired or used up (in the case of multi-seat licences).
There are several reasons for this:
The user may have installed the software on a notebook which is not always connected to the Internet.
If your company should experience licence server downtime, you don't want to prevent existing installations of your software from running.
Obligatory disclaimer & plug: the company I co-founded produces the OffByZero Cobalt licensing solution. With it, you can configure how frequently each individual licence calls home, and create offline licences that never call home. It also returns detailed information about connectivity, meaning that you can allow your application run even if the licence server is temporarily unavailable.