diff options
| author | keybuk@google.com <keybuk@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-21 02:34:00 +0000 |
|---|---|---|
| committer | keybuk@google.com <keybuk@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-03-21 02:34:00 +0000 |
| commit | 6652074712f84591150721953f6ed8049145256e (patch) | |
| tree | ba08278031be2edf40be1d8bbc6a31251fed5615 /chrome/browser/sync/internal_api/all_status.h | |
| parent | 80f07939e245cbccd898ee5742de79711d094914 (diff) | |
| download | chromium_src-6652074712f84591150721953f6ed8049145256e.zip chromium_src-6652074712f84591150721953f6ed8049145256e.tar.gz chromium_src-6652074712f84591150721953f6ed8049145256e.tar.bz2 | |
bluetooth: use better definitions of Paired
Recent Bluetooth specifications (such as V4.0 and HID 1.1) redefine "paired"
to be less confusing: pairing is the process of connecting two devices and
agreeing a basic link key, even if only temporary for that session. The
term "bonded" is used for a permanent link key that can be used for the
next connection.
While BlueZ still uses the older definitions, it makes sense for our
interface to use these new definitions, since it neatly divides devices
into "paired" and "not yet paired", with "bonded" a sub-category of
"paired".
BUG=none
TEST=verified on device
Change-Id: I29fc55fb9ffd0a20f8280e2b6371c3be459467b2
R=satorux@chromium.org,jhawkins@chromium.org,csilv@chromium.org,kevers@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9766005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@127884 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/sync/internal_api/all_status.h')
0 files changed, 0 insertions, 0 deletions