本机客户端应用程序与共享库(例如安全性)更新? [英] Native Client application vs shared libraries (e.g.security) updates?
问题描述
在传统模型中，当程序动态链接共享库时，作为副作用之一，它通常不必关心更新，因为当新版本(比如安全或性能修复)出现时，它已更新(通过某种 Uhix 上的某种包管理器或 Windows 上的等价物)，并且应用程序可以在下次运行新版本时受益.在此过程中，应用维护者无需执行任何步骤，即可让他/她的用户从新的、固定的库中受益.
In traditional model, when program does dynamic linking of shared library, than - as one of side effects - it, usually does not have to care about updates, as when new version (let's say with security or performance fix) comes, it's updated (by some kind of package manager on some Uhix or sth equivalent on Windows), and application can benefit on next run from new version. In such process, application maintainer does not have to perform any steps, in order for his/her users to benefit from new , fixed library.
它在 Native Client 中是如何工作的?那些库是打包的吗，所以每次有新版本的库来，开发者都得重新打包，或者是否有某种机制可以从某种方式或共享库中受益，或者自动重新打包此包(例如通过 Chrome 网上应用店)?
How does it work in Native Client? Are those libraries packed in package, so developer has to repackage every time new version of library comes, or is there some mechanism, either to benefit from some way or sharing libraries, or getting this package repacked automatically (for example by Chrome Web Store) ?
我已经目瞪口呆了:
并且找不到答案.(这并不意味着它不存在，我可能会错过某些东西).
and couldn't find answer. (It does not mean it's not there, I could miss sth).
推荐答案
根据我使用 NaCl 的经验，您的应用程序负责更新它所依赖的任何库，因为这些库必须随您的 NaCl 应用程序一起分发.浏览器向应用程序提供的任何库/API 除外，这些库/API 将与浏览器一起更新.
Based on my experience with NaCl, your app is responsible for updating any libraries it depends on, as those libraries are necessarily distributed with your NaCl application. The exception would be any libraries/APIs that the browser provides to the application, which would be updated along with the browser.
这篇关于本机客户端应用程序与共享库(例如安全性)更新?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
