Google advances Native Client Web browser technology
- 19 February, 2011 12:42
Google on Friday began offering a revamped SDK for its Native Client open source technology for running Web applications that execute native code inside a browser.
With the SDK, developers can start building Native Client applications ahead of the official launch. Plans call for putting Native Client technology inside the Google Chrome browser; until then, users cannot access the applications. Google did not have an estimate on when exactly Native Client would be supported in Chrome.
[ Also on InfoWorld.com: Blogger Neil McAllister calls Native API "Google's craziest idea yet." | Stay up to date on the key programming news and issues with InfoWorld's Developer World newsletter. Sign up today! ]
Also featured in the SDK is support for a set of interfaces dubbed "Pepper," providing compute, audio, and 2D Native Client modules. Pepper allows better access to browser systems for plug-ins.
The issue with native applications, including plug-ins, has been their access to the full machine -- even files. As a result, users are forced to make decisions about which applications to trust. Google with Native Client comes with rules that define valid code modules and limit access to a user's computer. It offers capabilities such as validation, which can prevent an invalid module from running.
Google had released a "sneak peek" of the SDK last year. In coming months, Google plans to add APIs for 3D graphics, local file storage and peer-to-peer networking. An ABI (application binary interface) is planned as well.
"Until the ABI becomes stable, Native Client will remain off by default," Stefansen said. "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."
Google has positioned Native Client as a technology intended to give developers full access to client CPU power while maintaining browser neutrality, OS portability, and safety in Web applications. It was built initially for 32- and 64-bit x86 systems running Windows, Mac OS, or Linux. The goal of the technology has been to enable development of Web applications that are richer and more dynamic.
This article, "Google advances Native Client browser technology," was originally published at InfoWorld.com. Follow the latest developments in business technology news and get a digest of the key stories each day in the InfoWorld Daily newsletter. For the latest business technology news, follow InfoWorld.com on Twitter.
Read more about developer world in InfoWorld's Developer World Channel.
Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.
- Google - InfoWorld
- Native Client: Google's craziest idea yet : Developer World - InfoWorld
- Developer World newsletter
- Native Client SDK - Google Code
- Google advances Native Client Web browser technology : Developer World - InfoWorld
- Business technology, IT news, product reviews and enterprise IT strategies - InfoWorld
- IT news and top technology headlines - InfoWorld
- InfoWorld Daily Newsletter - InfoWorld
- InfoWorld.com on Twitter
- Developer World - InfoWorld
Why change management doesn’t work
Larry Page wants to see your medical records
Dual-Persona Smartphones Not a BYOD Panacea
After two-year hiatus, EFF accepts bitcoin donations again
CIOs struggle to deliver timely mobile business apps: survey
Implementing A Security Analytics Architecture
According to the 2012 Verizon Data Breach Investigations report, 99% of breaches led to data compromise within “days” or less, whereas 85% of breaches took “weeks” or more to discover. This presents a significant challenge to security teams as it grants attackers extended periods of time within a victim’s environment. More “free time” leads to more stolen data and more digital damage. Principally, this is because today’s security measures aren’t designed to counter today’s more advanced threats. Read on.
The SPARC Difference - Reduce Risks, Cut Costs, Power Innovation
Despite current economic factors, IT investment continues to be fueled by the need for better and more agile IT capabilities to support an enterprise’s business strategy, as well as to keep up with the rapidly changing demands of the ‘always-on’ user. However, budgets are squeezed and executives are under pressure to reduce capital expenditure and streamline administrative costs. A key strategy is to consolidate and refresh existing IT infrastructures. Download now to find out what technology can add value and enable you to change the shape of your IT budget and, to transform IT into a force for change and innovation.
Moving to a Private Cloud? Infrastructure Really Matters!
The Cloud isn’t about locality. It is about quality of service delivery, cost, and whether the services consumed satisfy our objectives. For the enterprise, you need to select the right QoS to mitigate the inherent risks or you face the problem of losing data and the ability to execute operationally. Read on.