Refactor ProximityAuthUIDelegate functions to ProximityAuthClient.

Mirror ProximityAuthUIDelegate functions to ProximityAuthClient.

Both classes are embedder interfaces for the proximity_auth/ component to
delegate to Chrome. This CL is the first step to move the delegate functions
solely to ProximityAuthClient. The next CL will remove the
ProximityAuthUIDelegate class.

BUG=512230
Committed: https://crrev.com/13d636780595c920e4c53c0b8335ca9c85409079
Cr-Commit-Position: refs/heads/master@{#346005}

[Tim Song, 2015-08-25 03:02:43]

Patchset #1 (id:1) has been deleted

[Tim Song, 2015-08-25 03:02:50]

tengs@chromium.org changed reviewers:
+ sacomoto@chromium.org

[Tim Song, 2015-08-26 02:43:18]

tengs@chromium.org changed reviewers:
+ msarda@chromium.org

[sacomoto, 2015-08-27 11:29:31]

In the CL description, you meant ProximityAuthUIDelegate, right? If that's the
case, please update it before landing it.

LGTM with nit.

https://codereview.chromium.org/1316543003/diff/20001/chrome/browser/signin/c...
File chrome/browser/signin/chrome_proximity_auth_client.cc (right):

https://codereview.chromium.org/1316543003/diff/20001/chrome/browser/signin/c...
chrome/browser/signin/chrome_proximity_auth_client.cc:95:
device_classifier.set_device_type(cryptauth::CHROME);
This is sent to CryptAuth, right? Why does it need all this information?

[Tim Song, 2015-08-27 18:23:52]

https://codereview.chromium.org/1316543003/diff/20001/chrome/browser/signin/c...
File chrome/browser/signin/chrome_proximity_auth_client.cc (right):

https://codereview.chromium.org/1316543003/diff/20001/chrome/browser/signin/c...
chrome/browser/signin/chrome_proximity_auth_client.cc:95:
device_classifier.set_device_type(cryptauth::CHROME);
On 2015/08/27 11:29:31, sacomoto wrote:
> This is sent to CryptAuth, right? Why does it need all this information?

The people maintaining CryptAuth want to distinguish API calls made by different
platforms (e.g. Android vs. Chrome).

[Tim Song, 2015-08-27 20:24:30]

The CQ bit was checked by tengs@chromium.org

[commit-bot: I haz the power, 2015-08-27 20:24:40]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1316543003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1316543003/20001

[commit-bot: I haz the power, 2015-08-27 22:19:31]

Committed patchset #1 (id:20001)

[commit-bot: I haz the power, 2015-08-27 22:19:55]

Patchset 1 (id:??) landed as
https://crrev.com/13d636780595c920e4c53c0b8335ca9c85409079
Cr-Commit-Position: refs/heads/master@{#346005}

[sacomoto, 2015-08-28 14:40:23]

https://codereview.chromium.org/1316543003/diff/20001/chrome/browser/signin/c...
File chrome/browser/signin/chrome_proximity_auth_client.cc (right):

https://codereview.chromium.org/1316543003/diff/20001/chrome/browser/signin/c...
chrome/browser/signin/chrome_proximity_auth_client.cc:95:
device_classifier.set_device_type(cryptauth::CHROME);
On 2015/08/27 18:23:52, Tim Song wrote:
> On 2015/08/27 11:29:31, sacomoto wrote:
> > This is sent to CryptAuth, right? Why does it need all this information?
> 
> The people maintaining CryptAuth want to distinguish API calls made by
different
> platforms (e.g. Android vs. Chrome).

I see. Thanks.