跳过 AIR 更新
假设我有一个 AIR 应用程序需要更新：之前的版本号是 0.0.1，当前版本号是 0.0.2。现在，上述应用程序已安装在许多不同的电脑上。我只想根据特定 ID 更新某些客户端。是否可以跳过某些客户端的更新过程？
Imagine I have an AIR application to update: the preceding version number is 0.0.1, the current one is 0.0.2. Now, the preceding app is installed on many different pcs. I want to update ONLY some clients, based on a particular ID. Is it possible to skip update process for some clients?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
简短的回答是肯定的，这是可能的。如果您编写自己的代码来检查更新，将更新下载到本地文件，然后调用 System:Updater.update() 或 Air.update:ApplicationUpdater.installFromAIRFile() 旧的AIRUpdater.js 示例可以帮助您入门。
问题是您必须使用新代码更新所有 0.0.1 客户端，然后他们才能对 0.0.2 做出决定。如果您没有好的方法来确保在部署下一个版本之前它们已全部更新，您可能需要更改中间版本中更新描述符文件的位置。否则，您最终可能会得到落后的 0.0.1，它会跳过中间版本并更新到 0.0.2，而无需进行 ID 检查。
我还没有尝试过，但使用 AIR 1.5 中较新的 Air.update:ApplicationUpdater 类并将您的 ID 检查放入 updateStatus 事件中可能会更容易。
The short answer is yes, it is possible. You can do just about whatever you need if you write your own code to check for updates, download updates to a local file, then call System:Updater.update() or Air.update:ApplicationUpdater.installFromAIRFile() The old AIRUpdater.js example from AIR 1.0 can get your started.
The problem is you'll have to update all of your 0.0.1 clients with new code before they can make a decision on 0.0.2. And if you don't have a good way to ensure they've all been updated before deploying your next version, you'll probably want to change the location of the update descriptor file in your intermediate version. Otherwise you may end up with straggler 0.0.1's that skip the intermediate version and update to 0.0.2 without your ID checking.
And I haven't tried this yet, but it might be even easier to use the newer Air.update:ApplicationUpdater class from AIR 1.5 and put your ID checking in the updateStatus event.