问题描述
Google已将Google Chrome中使用的自动更新机制作为开源。
Google has open-sourced the auto update mechanism used in Google Chrome as Omaha.
对于任何不是Google的人来说，配置似乎相当复杂和困难。在项目中使用奥马哈的经历是什么？是否可以推荐？
It seems quite complicated and difficult to configure for anybody who isn't Google. What is the experience using Omaha in projects? Can it be recommended?
推荐答案
我们使用奥马哈产品。最初，改变硬编码的URL和字符串有相当多的工作。此外，服务器不是开源的，但协议有详细的文档记录，因此使用Google App Engine创建兼容服务器并不困难。
We use Omaha for our products. Initially there was quite a bit of work to change hardcoded URLs and strings. Also the server is not open source, but the protocol is well documented so it was not difficult to create a compatible server using Google App Engine.
开球不会有任何遗憾我们的老客户更新解决方案，并与奥马哈。
There are no regrets with ditching our old client update solution and going with Omaha.
这篇关于Google'奥马哈'（Chrome的自动更新引擎）的体验如何？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！