From 34997731954015ce4e946ce696d487db17b848c1 Mon Sep 17 00:00:00 2001
From: Luan Nguyen
Date: Mon, 13 Apr 2015 11:02:32 -0700
Subject: cherrypick from lmp-docs docs: Add Channel API summary for Wear.
Original Change-Id: I447e58264e142a5e04aaf520d31dc4ced2506ecb
bug: 20089257
Change-Id: I25ad962ef847574d2152229ebb2ce268483c2a68
---
docs/html/training/wearables/data-layer/index.jd | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
(limited to 'docs/html/training')
diff --git a/docs/html/training/wearables/data-layer/index.jd b/docs/html/training/wearables/data-layer/index.jd
index 85b2c33..b49ea4d 100644
--- a/docs/html/training/wearables/data-layer/index.jd
+++ b/docs/html/training/wearables/data-layer/index.jd
@@ -58,6 +58,30 @@ the data layer:
WearableListenerService
lets you listen for changes only when the user is actively using your app.
+
+ Channel
+
+ You can use the
+ ChannelApi
+ class to transfer large data items, such as music and movie files, from a handheld to a wearable
+ device. The Channel API for data transfer has the following benefits:
+
+ - Transfer large data files between two or more connected devices, without
+ the automatic synchronization provided when using
+
Asset
+ objects attached to
+ DataItem
+ objects. The Channel API saves disk space unlike the
+ DataApi
+ class, which creates a copy of the assets on the local device before synchronizing with
+ connected devices.
+ - Reliably send a file that is too large in size to send using the
+
MessageApi
+ class.
+ - Transfer streamed data, such as music pulled from a network server or voice
+ data from the microphone.
+
+
Warning:
--
cgit v1.1