| commit | 902f5c9d70d03d53e07e30b901fb323a061e5c00 | |
| author | sacomoto <sacomoto@chromium.org> | |
| Wed, 24 Jun 2015 10:18:49 +0000 (24 03:18 -0700) | ||
| committer | Commit bot <commit-bot@chromium.org> | |
| Wed, 24 Jun 2015 10:19:15 +0000 (24 10:19 +0000) | ||
| tree | 5816dff562958b5fcde2909d1cdd25b6bd6c5bc6 | treesnapshot (tar.gz zip) |
| parent | a5f249ed818221e7df37f7fb295a6312464caf73 | commitdiff |
Handling BLE disconnect events in ProximityAuthBleSystem.
There are two kinds of disconnect events for
proximity_auth::BluetoothLowEnergyConnection objects:
i) An IN_PROGRESS BLE connection fails to complete;
ii) A CONNECTED BLE connection disconnects.
The first kind should be handled by the
proximity_auth::BluetoothLowEnergyConnectionFinder class. As its
contracts guarantee that CONNECTED BLE connection will be passed as
callback to its caller.
Then, any further disconnect event (ii) should be handled by the
object calling the BLE connection finder.
BUG=
Review URL: https://codereview.chromium.org/1196183007
Cr-Commit-Position: refs/heads/master@{#335899}
There are two kinds of disconnect events for
proximity_auth::BluetoothLowEnergyConnection objects:
i) An IN_PROGRESS BLE connection fails to complete;
ii) A CONNECTED BLE connection disconnects.
The first kind should be handled by the
proximity_auth::BluetoothLowEnergyConnectionFinder class. As its
contracts guarantee that CONNECTED BLE connection will be passed as
callback to its caller.
Then, any further disconnect event (ii) should be handled by the
object calling the BLE connection finder.
BUG=
Review URL: https://codereview.chromium.org/1196183007
Cr-Commit-Position: refs/heads/master@{#335899}