沙盒插件架构
我在谷歌上搜索插件架构，我对如何实现它的常识感到满意。现在我进一步寻找沙盒架构。基本上我的意思是一个带有插件的应用程序，插件崩溃不会使整个应用程序崩溃，并且插件可以重新加载。 我找不到好的文档。 我知道 Firefox 实现了它（崩溃的 flash 插件不会影响整个 FF 并且可以重新加载） 谢谢！
I was googling and searching SO for plugin architecture and I'm satisfied by general knowledge on how to implement it. Now I went further to look for a sandboxed architecture. Basically what I mean is an application with plugin whereby crashing in plugin won't crash the whole app and the plugin can be reloaded.
I cannot find good documentation.
I know Firefox implements it (crashing flash plugin does not affect whole FF thing and can be reloaded)
Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
拥有真正的沙盒架构（其中插件无法直接崩溃父应用程序的进程或损坏其内存）的唯一方法是将其放入具有单独内存空间的单独操作系统进程中。执行此操作时，您将需要依赖操作系统的进程间通信设施（管道、套接字、远程过程调用、内存映射文件、共享内存、同步对象等）来与插件交互。
The only way you can have a truly sandboxed architecture wherein a plug-in cannot directly crash the parent application's process or corrupt its memory is by placing it into a separate OS process, with a separate memory space. When doing this, you will need to rely on interprocess communication facilities of the OS (pipes, sockets, remote procedure calls, memory mapped files, shared memory, synchronization objects, etc.) to interact with the plug-in.
Google 的原生客户端技术可能比您想要的更全面，但可能值得一读。
Google's native client technology may be more thorough than what you were looking for, but it might be worth a read.