| |||||||||||||
Small corrections...Small corrections...Posted Jul 28, 2011 9:05 UTC (Thu) by khim (subscriber, #9252)Parent article: Google's Native Client forges ahead
Disclaimer: I'm NaCl developer and we KNOW our documentation suck. We are working on it. The NaCl plugin isolates code in the sandbox by using the memory segmentation available in processes, thus providing a contiguous, private address space for each component currently 256MB in size. This is old information (year or so old). Today we provide 1GB on x86 and ARM and 4GB on x86-64. 256MB are reserved for code and 768MB are available for data. Loaded modules are also read-only in memory, to prevent self-modifying code. We support some very limited modifications using specialized "syscalls". Enough to support V8 and Mono. NaCl also provides two higher-level mechanisms built on top of IMC: the Simple Remote Procedure Call (SRPC) facility, and an implementation of the traditional Netscape Plugin API (NPAPI). Direct SRPC access is deprecated and NPAPI was completely replaced with PPAPI. This is the change I personally don't like all that much, but it was price to pay to be accepted by Chrome :-(
(Log in to post comments)
Small corrections... Posted Jul 28, 2011 17:27 UTC (Thu) by loevborg (guest, #51779) [Link]
As you're involved in the project, do you have an estimate when we will see, say, quake working in a stable chrome version?
Good question... Posted Jul 29, 2011 12:46 UTC (Fri) by khim (subscriber, #9252) [Link] As you're involved in the project, do you have an estimate when we will see, say, quake working in a stable chrome version? Who knows? There are two problems: So the answer is, sadly: not for a long time yet. With M14 (should reach developer channel in about six weeks and stable channel in about three months) you should be able to put Quake with some kind of original artwork in Chrome Store if you would like it.
|
|||||||||||||