Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit e152b793 authored by Robert Ly's avatar Robert Ly
Browse files

docs: remove fire and forget language from wear docs

Change-Id: I0a8d83ba0db24f1232d4c729f298c6af04c048b3
parent 1b12b1dc
Loading
Loading
Loading
Loading
+1 −1
Original line number Diff line number Diff line
@@ -28,7 +28,7 @@ the data layer:</p>

  <dt><b>Messages</b></dt>
  <dd>The <a href="{@docRoot}reference/com/google/android/gms/wearable/MessageApi.html"><code>MessageApi</code></a> class
  can send messages designed for "fire-and-forget" commands, such as controlling a handheld's
  can send messages and is good for remote procedure calls (RPC), such as controlling a handheld's
  media player from the wearable or starting an intent on the wearable from the handheld.
  The system always delivers the message when the handheld and wearable are connected and delivers
  an error when the devices are disconnected. Messages are great for one-way requests or for a
+2 −2
Original line number Diff line number Diff line
@@ -23,8 +23,8 @@ and attach the following items to the message:</p>
</ul>
<p>
Unlike data items, there is no syncing between the handheld and wearable apps.
Messages are a one-way communication mechanism that's meant for
"fire-and-forget" tasks, such as sending a message to the wearable
Messages are a one-way communication mechanism that's good for remote procedure calls (RPC),
such as sending a message to the wearable
to start an activity. You can also use messages in request/response model
where one side of the connection sends a message, does some work,
sends back a response message.</p>