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

native_client_sdk/doc_generated/devguide/coding/message-system.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="messaging-system">
 <span id="message-system"></span><h1 id="messaging-system"><span id="message-system"></span>Messaging System</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#reference-information" id="id2">Reference information</a></li>
 <li><p class="first"><a class="reference internal" href="#introduction-to-the-messaging-system" id="id3">Introduction to the messaging system</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#design-of-the-messaging-system" id="id4">Design of the messaging system</a></li>
@@ skipping 30 matching lines @@
 <aside class="note">
 The &#8220;Hello, World&#8221; example for getting started with NaCl is used here to
 illustrate basic programming techniques. You can find this code in
 the <code>/getting_started/part2</code> directory in the Native Client SDK download.
 </aside>
 <section id="reference-information">
 <h2 id="reference-information">Reference information</h2>
 <p>For reference information related to the Pepper messaging API, see the
 following documentation:</p>
 <ul class="small-gap">
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_instance">pp::Instance class</a> HandleMessage(), PostMessage())</li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_module">pp::Module class</a></li>
-<li><a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_var">pp::Var class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_instance">pp::Instance class</a>
+HandleMessage(), PostMessage())</li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_module">pp::Module class</a></li>
+<li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_var">pp::Var class</a></li>
 </ul>
 </section><section id="introduction-to-the-messaging-system">
 <h2 id="introduction-to-the-messaging-system">Introduction to the messaging system</h2>
-<p>Native Client modules and JavaScript communicate by sending messages
-to each other. The most basic form of a message is a string.  Messages
-support many JavaScript types, including ints, arrays, array buffers,
-and dictionaries (see <a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_var">pp::Var</a>,
-<a class="reference external" href="https://developers.google.com/native-client/peppercpp/classpp_1_1_var_array_buffer">pp:VarArrayBuffer</a>,
-and the general <a class="reference external" href="https://developers.google.com/native-client/pepperc/struct_p_p_b___messaging__1__0">messaging system documentation</a>).
-It&#8217;s up to you to decide on the type of message and define how to
-process the messages on both the JavaScript and Native Client
-side. For the &#8220;Hello, World&#8221; example, we will work with string-typed
-messages only.</p>
+<p>Native Client modules and JavaScript communicate by sending messages to each
+other. The most basic form of a message is a string.  Messages support many
+JavaScript types, including ints, arrays, array buffers, and dictionaries (see
+<a class="reference external" href="h/native-client/pepper_stable/cpp/classpp_1_1_var">pp::Var</a>,
+<a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_var_array_buffer">pp:VarArrayBuffer</a>, and the
+general <a class="reference external" href="/native-client/pepper_stable/c/struct_p_p_b___messaging__1__0">messaging system documentation</a>).  It&#8217;s up to
+you to decide on the type of message and define how to process the messages on
+both the JavaScript and Native Client side. For the &#8220;Hello, World&#8221; example, we
+will work with string-typed messages only.</p>
 <p>When JavaScript posts a message to the Native Client module, the
 Pepper <code>HandleMessage()</code> function is invoked on the module
 side. Similarly, the Native Client module can post a message to
 JavaScript, and this message triggers a JavaScript event listener for
 <code>message</code> events in the DOM. (See the W3C specification on
 <a class="reference external" href="http://www.w3.org/TR/DOM-Level-2-Events/events.html">Document Object Model Events</a> for more
 information.) In the &#8220;Hello, World&#8221; example, the JavaScript functions for
 posting and handling messages are named <code>postMessage()</code> and
 <code>handleMessage()</code> (but any names could be used). On the Native Client
 C++ side, the Pepper Library functions for posting and handling
@@ skipping 88 matching lines @@
 }
 </pre>
 </section></section><section id="native-client-module">
 <h3 id="native-client-module">Native Client module</h3>
 <p>The C++ code in the Native Client module of the &#8220;Hello, World&#8221; example:</p>
 <ol class="arabic simple">
 <li>Implements <code>pp::Instance::HandleMessage()</code> to handle messages sent
 by the JavaScript.</li>
 <li>Processes incoming messages. This example simply checks that JavaScript
 has sent a &#8220;hello&#8221; message and not some other message.</li>
-<li>Calls <code>PostMessage()</code> to send an acknowledgement back to the
-JavaScript code.  The acknowledgement is a string in the form of a <code>Var</code>
-that the JavaScript code can process.  In general, a <code>pp::Var</code> can be
-several JavaScript types, see the
-<a class="reference external" href="https://developers.google.com/native-client/pepperc/struct_p_p_b___messaging__1__0">messaging system documentation</a>.</li>
+<li>Calls <code>PostMessage()</code> to send an acknowledgement back to the JavaScript
+code.  The acknowledgement is a string in the form of a <code>Var</code> that the
+JavaScript code can process.  In general, a <code>pp::Var</code> can be several
+JavaScript types, see the <a class="reference external" href="/native-client/pepper_stable/c/struct_p_p_b___messaging__1__0">messaging system documentation</a>.</li>
 </ol>
 <pre class="prettyprint">
 class HelloTutorialInstance : public pp::Instance {
  public:
   // ...
 
   // === Step 1: Implement the HandleMessage function. ===
   virtual void HandleMessage(const pp::Var&amp; var_message) {
 
     // === Step 2: Process the incoming message. ===
@@ skipping 177 matching lines @@
     pp::VarArray keys = dictionary.GetKeys();
     // ...
   } else {
     // ...
   }
 }
 </pre>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}