| Index: native_client_sdk/doc_generated/devguide/coding/nacl_io.html
|
| diff --git a/native_client_sdk/doc_generated/devguide/coding/nacl_io.html b/native_client_sdk/doc_generated/devguide/coding/nacl_io.html
|
| index 757899a56f420bed3e8c32f2085b1e5fdb7c0fe1..37dc5a35b696c6e345a982dca5551cabd47facf4 100644
|
| --- a/native_client_sdk/doc_generated/devguide/coding/nacl_io.html
|
| +++ b/native_client_sdk/doc_generated/devguide/coding/nacl_io.html
|
| @@ -12,7 +12,7 @@
|
| <li><a class="reference internal" href="#a-look-at-the-code" id="id5">A look at the code</a></li>
|
| </ul>
|
| </li>
|
| -<li><a class="reference internal" href="#reference-information" id="id6">Reference information</a></li>
|
| +<li><a class="reference internal" href="#reference-information" id="id6">Reference Information</a></li>
|
| </ul>
|
|
|
| </div><h2 id="introduction">Introduction</h2>
|
| @@ -22,16 +22,19 @@ Its primary function is to allow code that uses these standard APIs to be
|
| compiled and used in a Native Client module. The library is included as part
|
| of Native Client SDK and is implemented in on top of Pepper API.</p>
|
| <p>Since Native Client modules cannot access the host machine’s file system
|
| -directly, nacl_io provides several alternative filesystem types which
|
| -can be used by the application. For example, the Chrome browser supports the
|
| -<a class="reference external" href="http://www.html5rocks.com/en/tutorials/file/filesystem/">HTML5 File System API</a> which provides
|
| -access to a protected area of the local file system. This filesystem can
|
| -be accessed by an HTML page using JavaScript commands, and also by a Native
|
| -Client module using the Pepper <a class="reference internal" href="/native-client/devguide/coding/file-io.html"><em>File IO API</em></a>. With nacl_io
|
| -a Native Client application can mount an HTML5 filesystem and access it via
|
| -standard POSIX I/O function such as <code>fopen</code>, <code>fseek</code>, <code>fread</code>,
|
| -<code>fwrite</code>, and <code>fclose</code>, or their low level UNIX counterparts <code>open</code>,
|
| -<code>lseek</code>, <code>read</code>, <code>write</code> and <code>close</code>.</p>
|
| +directly, nacl_io provides several alternative filesystem types which can be
|
| +used by the application. For example, the Chrome browser supports the <a class="reference external" href="http://www.html5rocks.com/en/tutorials/file/filesystem/">HTML5
|
| +File System API</a>
|
| +which provides access to a protected area of the local file system. This
|
| +filesystem can be accessed by an HTML page using JavaScript commands, and also
|
| +by a Native Client module using the Pepper <a class="reference internal" href="/native-client/devguide/coding/file-io.html"><em>File IO API</em></a>.</p>
|
| +<p>With nacl_io a Native Client application can mount an HTML5 filesystem and
|
| +access it via standard POSIX I/O function such as <code>fopen</code>, <code>fseek</code>,
|
| +<code>fread</code>, <code>fwrite</code>, and <code>fclose</code>, or their low level UNIX counterparts
|
| +<code>open</code>, <code>lseek</code>, <code>read</code>, <code>write</code> and <code>close</code>. Unlike most input/output
|
| +for nacl_io, logging writes directly to the <code>stderr</code> stream of the NaCl
|
| +process. It deliberately bypasses the standard library functions implemented in
|
| +nacl_io to avoid circular calls to itself.</p>
|
| <p>As well as the HTML5 file system, nacl_io provides several other file system
|
| types which are described in the table below:</p>
|
| <table border="1" class="docutils">
|
| @@ -203,7 +206,7 @@ int HandleFwrite(int num_params, char** params, char** output) {
|
| return 0;
|
| }
|
| </pre>
|
| -<h2 id="reference-information">Reference information</h2>
|
| +<h2 id="reference-information">Reference Information</h2>
|
| <p>The example discussed here is included in the SDK in the directory
|
| <code>examples/demo/nacl_io_demo</code>.</p>
|
| <p>The nacl_io library is included in the SDK toolchain and is not a part of the
|
|
|