1{{+bindTo:partials.standard_nacl_article}} 2 3<section id="glossary"> 4<span id="id1"></span><h1 id="glossary"><span id="id1"></span>Glossary</h1> 5<p>This glossary defines terms and names commonly used throughout the Native Client 6documentation.</p> 7<dl class="docutils"> 8<dt>asynchronous programming</dt> 9<dd>In the asynchronous programming model, function calls are executed and return 10immediately without waiting for a response. Using this model, function calls 11are non-blocking; the web browser continues its main thread of execution 12and gets notified of asynchronous call completion through callbacks or some 13other mechanism.</dd> 14<dt>focus events</dt> 15<dd>Events that indicate whether certain parts of a web page are 16in or out of focus.</dd> 17<dt>input events</dt> 18<dd>Events that occur when an input device (such as keyboard or mouse) 19is used to interact with an module instance.</dd> 20<dt>instance</dt> 21<dd>A rectangle on a web page that is managed by a Native Client module (the 22rectangle can have <code>width=0</code> and <code>height=0</code>, which means that nothing is 23drawn on the page).</dd> 24<dt>manifest file</dt> 25<dd>A file containing metadata or information about accompanying files.</dd> 26<dt>message events</dt> 27<dd>Events used to pass data between JavaScript and the Native Client 28module (see the <a class="reference internal" href="/native-client/devguide/coding/message-system.html"><em>Messaging System</em></a> section).</dd> 29<dt>module</dt> 30<dd>Depending on context, “module” may mean one of two things. First, it may be a 31general short-term for for “Native Client module”—compiled C/C++ code 32produced with a Native Client toolchain (for example PNaCl). See 33<a class="reference internal" href="/native-client/overview.html#link-how-nacl-works"><em>How Native Client works</em></a> for more details. 34Second, it may refer to a concrete implementation of the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_module">pp::Module class</a> for some Native 35Client module.</dd> 36<dt>progress events</dt> 37<dd>Events generated by the Native Client runtime system during the 38module loading process.</dd> 39<dt>Var</dt> 40<dd>An object in a Native Client module that corresponds to a JavaScript 41variable.</dd> 42<dt>view change events</dt> 43<dd>Events that occur when a change in the browser affects the 44module instance (such as resizing the browser window or going to 45and from fullscreen mode).</dd> 46<dt>web workers</dt> 47<dd><a class="reference external" href="http://en.wikipedia.org/wiki/Web_Workers">Web workers</a> provide a 48mechanism for running heavy-weight JavaScript code on background threads 49so that the main web page can continue to respond to user interaction. 50Web pages interact with web workers by using <code>postMessage()</code> to send 51messages. The way a web page interacts with a Native Client module 52is analogous to the way it interacts with web workers.</dd> 53</dl> 54</section> 55 56{{/partials.standard_nacl_article}} 57