[NaCl SDK Docs] Remove links to developers.google.com

native_client_sdk/doc_generated/devguide/coding/file-io.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="file-i-o">
 <span id="devguide-coding-fileio"></span><h1 id="file-i-o"><span id="devguide-coding-fileio"></span>File I/O</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#introduction" id="id2">Introduction</a></li>
 <li><a class="reference internal" href="#reference-information" id="id3">Reference information</a></li>
 <li><p class="first"><a class="reference internal" href="#local-file-i-o" id="id4">Local file I/O</a></p>
 <ul class="small-gap">
@@ skipping 19 matching lines @@
 <li><a class="reference internal" href="#loading-a-file" id="id18">Loading a file</a></li>
 <li><a class="reference internal" href="#id1" id="id19">Deleting a file</a></li>
 <li><a class="reference internal" href="#listing-files-in-a-directory" id="id20">Listing files in a directory</a></li>
 <li><a class="reference internal" href="#making-a-new-directory" id="id21">Making a new directory</a></li>
 </ul>
 </li>
 </ul>
 
 </div><section id="introduction">
 <h2 id="introduction">Introduction</h2>
-<p>This chapter describes how to use the <a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_file_i_o">FileIO API</a>
-to read and write files using a local secure data store.</p>
+<p>This chapter describes how to use the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_file_i_o">FileIO API</a> to read and write
+files using a local secure data store.</p>
 <p>You might use the File IO API with the URL Loading APIs to create an overall
 data download and caching solution for your NaCl applications. For example:</p>
 <ol class="arabic simple">
 <li>Use the File IO APIs to check the local disk to see if a file exists that
 your program needs.</li>
 <li>If the file exists locally, load it into memory using the File IO API. If
 the file doesn&#8217;t exist locally, use the URL Loading API to retrieve the
 file from the server.</li>
 <li>Use the File IO API to write the file to disk.</li>
 <li>Load the file into memory using the File IO API when needed by your
 application.</li>
 </ol>
 <p>The example discussed in this chapter is included in the SDK in the directory
 <code>examples/api/file_io</code>.</p>
 </section><section id="reference-information">
 <h2 id="reference-information">Reference information</h2>
 <p>For reference information related to FileIO, see the following documentation:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/file__io_8h">file_io.h</a> - API
-to create a FileIO object</li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/file__ref_8h">file_ref.h</a> - API
-to create a file reference or &#8220;weak pointer&#8221; to a file in a file system</li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/file__system_8h">file_system.h</a> -
-API to create a file system associated with a file</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/file__io_8h">file_io.h</a> - API to create a
+FileIO object</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/file__ref_8h">file_ref.h</a> - API to create
+a file reference or &#8220;weak pointer&#8221; to a file in a file system</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/file__system_8h">file_system.h</a> - API to
+create a file system associated with a file</li>
 </ul>
 </section><section id="local-file-i-o">
 <h2 id="local-file-i-o">Local file I/O</h2>
 <p>Chrome provides an obfuscated, restricted area on disk to which a web app can
 safely <a class="reference external" href="https://developers.google.com/chrome/whitepapers/storage#persistent">read and write files</a>. The
 Pepper FileIO, FileRef, and FileSystem APIs (collectively called the File IO
 APIs) allow you to access this sandboxed local disk so you can read and write
 files and manage caching yourself. The data is persistent between launches of
 Chrome, and is not removed unless your application deletes it or the user
 manually deletes it. There is no limit to the amount of local data you can
 use, other than the actual space available on the local drive.</p>
 <section id="enabling-local-file-i-o">
 <span id="enabling-file-access"></span><span id="quota-management"></span><h3 id="enabling-local-file-i-o"><span id="enabling-file-access"></span><span id="quota-management"></span>Enabling local file I/O</h3>
 <p>The easiest way to enable the writing of persistent local data is to include
-the <a class="reference external" href="http://developer.chrome.com/extensions/declare_permissions.html#unlimitedStorage">unlimitedStorage permission</a>
-in your Chrome Web Store manifest file. With this permission you can use the
-Pepper FileIO API without the need to request disk space at run time. When
-the user installs the app Chrome displays a message announcing that the app
-writes to the local disk.</p>
+the <a class="reference external" href="/extensions/declare_permissions#unlimitedStorage">unlimitedStorage permission</a> in your Chrome Web Store
+manifest file. With this permission you can use the Pepper FileIO API without
+the need to request disk space at run time. When the user installs the app
+Chrome displays a message announcing that the app writes to the local disk.</p>
 <p>If you do not use the <code>unlimitedStorage</code> permission you must include
 JavaScript code that calls the <a class="reference external" href="http://updates.html5rocks.com/2011/11/Quota-Management-API-Fast-Facts">HTML5 Quota Management API</a> to
 explicitly request local disk space before using the FileIO API. In this case
 Chrome will prompt the user to accept a requestQuota call every time one is
 made.</p>
 </section><section id="testing-local-file-i-o">
 <h3 id="testing-local-file-i-o">Testing local file I/O</h3>
 <p>You should be aware that using the <code>unlimitedStorage</code> manifest permission
 constrains the way you can test your app. Three of the four techniques
 described in <a class="reference internal" href="/native-client/devguide/devcycle/running.html"><em>Running Native Client Applications</em></a>
@@ skipping 394 matching lines @@
     PP_MAKEDIRECTORYFLAG_NONE, pp::BlockUntilComplete());
 if (result != PP_OK) {
   ShowErrorMessage(&quot;Make directory failed&quot;, result);
   return;
 }
 ShowStatusMessage(&quot;Make directory success&quot;);
 </pre>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}