Native Client: Ready for takeoff!
During the past months, we have been intensively working on translating the Native Client to a new browser plug-in API, Pepper ( Pepper is a set of NPAPI extensions proposed by Google. Comment. Trans. ). Native Client is a technology that allows you to execute machine code directly in the browser, and it is transparent and secure. Today, with the release of the updated SDK for the Native Client , we have made significant progress towards making the Native Client modules as portable and secure as JavaScript.
The SDK now contains a comprehensive set of Pepper interfaces for Native Client modules responsible for computing, audio, and 2D. These interfaces are practically stable, with the exception of a few important exceptions indicated in the release notes .
In addition, we focused on improving security: added auto-update and an external sandbox. This made it possible to remove some of the restrictions that were used in previous versions for developers. In addition to working on security, we also implemented a mechanism for obtaining Native Client modules based on the target machine's processor instruction set, so that developers no longer have to worry about this.
We are pleased to watch as the Native Client is gradually becoming a technology that is ready for use by developers. In the coming months, we will add an API for 3D graphics, local file storage, web sockets, P2P connections, and many others. We will also work on dynamic shared objects (Dynamic Shared Object, DSO), a function that in the future will ensure the stability of the binary interface (ABI).
')
As long as the ABI is not stable, the Native Client will remain disabled by default. However, given the success we have achieved, you can already enable this technology and use it constantly in versions of Chrome, starting with the tenth, through the about: flags tab, or through a command line parameter.
The main goal of this release is to give developers the opportunity to start creating Native Client modules for Chrome apps. Please follow this blog to find out more quickly, as well as join our group to get answers to questions, feedback and inclusion in the Native Client community.
The SDK now contains a comprehensive set of Pepper interfaces for Native Client modules responsible for computing, audio, and 2D. These interfaces are practically stable, with the exception of a few important exceptions indicated in the release notes .
In addition, we focused on improving security: added auto-update and an external sandbox. This made it possible to remove some of the restrictions that were used in previous versions for developers. In addition to working on security, we also implemented a mechanism for obtaining Native Client modules based on the target machine's processor instruction set, so that developers no longer have to worry about this.
We are pleased to watch as the Native Client is gradually becoming a technology that is ready for use by developers. In the coming months, we will add an API for 3D graphics, local file storage, web sockets, P2P connections, and many others. We will also work on dynamic shared objects (Dynamic Shared Object, DSO), a function that in the future will ensure the stability of the binary interface (ABI).
')
As long as the ABI is not stable, the Native Client will remain disabled by default. However, given the success we have achieved, you can already enable this technology and use it constantly in versions of Chrome, starting with the tenth, through the about: flags tab, or through a command line parameter.
The main goal of this release is to give developers the opportunity to start creating Native Client modules for Chrome apps. Please follow this blog to find out more quickly, as well as join our group to get answers to questions, feedback and inclusion in the Native Client community.
Source: https://habr.com/ru/post/114114/
All Articles