Since (Native Client Web Plugin) refers to a specific technology architecture rather than a single famous academic paper, the most appropriate paper to provide is the foundational publication by Google that introduced the technology to the scientific community. Flashzap — Motorola
Prior to Native Client (NaCl), web applications were limited to JavaScript, which is interpreted and generally slower than native code. Developers who needed high performance (e.g., games, video editing, scientific simulations) had to rely on browser plugins like Flash or ActiveX, which often had significant security vulnerabilities and platform compatibility issues. I Key Generator For Asc Timetable Work File
Below is the citation and abstract information for the seminal paper defining this technology, followed by a summary of why this architecture was significant. Title: Native Client: A Sandbox for Portable, Untrusted x86 Native Code Authors: Brad Chen, David Tarditi, Bennet Yee, et al. Publication: Proceedings of the 2009 IEEE Symposium on Security and Privacy (SP '09) Publisher: IEEE Computer Society Year: 2009 Abstract "Native Client is a sandbox for running untrusted x86 native code. It aims to give browser-based applications the computational performance of native applications without compromising safety. Native Client uses static binary analysis to detect security defects in untrusted x86 code, and dynamic fault isolation to limit the effects of bugs in untrusted code. We describe the design and implementation of Native Client, and evaluate its performance on compute-intensive benchmarks. We find that Native Client imposes a low performance penalty—typically less than 5%—while providing strong security guarantees." Overview of the Technology If you are researching "naclwebplugin" for a computer science course or technical review, the paper above covers the following key concepts that defined the plugin architecture: