Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

am e152b793: docs: remove fire and forget language from wear docs

Browse Source 
* commit 'e152b793e5f56ac9d73d0b3e3e191fea6b0ba1e5':
  docs: remove fire and forget language from wear docs
This commit is contained in:
Robert Ly
2014-09-15 19:27:18 +00:00
committed by Android Git Automerger
parent 02480cbffa e152b793e5
commit d00b110a3b
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/html/training/wearables/data-layer/index.jd
View File

@@ -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

4
docs/html/training/wearables/data-layer/messages.jd
View File

@@ -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>