Native Client SDK Released with Pepper Interfaces Support

Native Client is an open source technology that allows you to build web applications that seamlessly and safely execute native compiled code inside the browser. Over the last few months we have been hard at work getting Native Client ready to support the new Pepper plug-in interface. Google today, reached an important milestone in an […]

Native Client is an open source technology that allows you to build web applications that seamlessly and safely execute native compiled code inside the browser. Over the last few months we have been hard at work getting Native Client ready to support the new Pepper plug-in interface. Google today, reached an important milestone in an efforts to make Native Client modules as portable and secure as JavaScript, by making available a first release of the revamped Native Client SDK.

The SDK now includes support for a comprehensive set of Pepper interfaces for compute, audio, and 2D Native Client modules. These interfaces are close to being stable, with some important exceptions that're listed in the release notes.

"In addition, we've focused on improving security. We have enabled auto-update and an outer sandbox. This allowed us to remove the expiration date and localhost security restrictions we had adopted in previous research-focused releases. Beyond security, we've also improved the mechanism for fetching Native Client modules based on the instruction set architecture of the target machine, so developers don't need to worry about this any more," said Google.

Until the ABI becomes stable, Native Client will remain off by default. However, given the progress we've made, you can now sticky-enable Native Client in Chrome 10+ through the about:flags dialog. Otherwise, you can continue using a command line flag to enable Native Client when you want to.

[tags]native client,pepper[/tags]

[Source]