Updating the remote_security_key to use the new message processing classes.

Updating the remote_security_key to use the new message processing classes.

This change updates the main function used in the remote_security_key process
so it creates the appropriate classes to handle IPC and STDIO messages and then
starts the handlers to process those messages until it is told to quit.

BUG=584463
Committed: https://crrev.com/e7680c79e7ebc47ffed579fe29c1bf574089999d
Cr-Commit-Position: refs/heads/master@{#385543}

[joedow, 2016-04-05 21:39:40]

joedow@chromium.org changed reviewers:
+ sergeyu@chromium.org

[joedow, 2016-04-05 21:39:40]

PTAL!

Thanks,
Joe

[joedow, 2016-04-06 16:24:20]

Ping!

[Sergey Ulanov, 2016-04-06 20:07:25]

lgtm

[joedow, 2016-04-06 20:12:25]

The CQ bit was checked by joedow@chromium.org

[commit-bot: I haz the power, 2016-04-06 20:12:52]

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

[commit-bot: I haz the power, 2016-04-06 20:22:24]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-04-06 20:24:03]

Description was changed from

==========
Updating the remote_security_key to use the new message processing classes.

This change updates the main function used in the remote_security_key process
so it creates the appropriate classes to handle IPC and STDIO messages and then
starts the handlers to process those messages until it is told to quit.

BUG=584463
==========

to

==========
Updating the remote_security_key to use the new message processing classes.

This change updates the main function used in the remote_security_key process
so it creates the appropriate classes to handle IPC and STDIO messages and then
starts the handlers to process those messages until it is told to quit.

BUG=584463

Committed: https://crrev.com/e7680c79e7ebc47ffed579fe29c1bf574089999d
Cr-Commit-Position: refs/heads/master@{#385543}
==========

[commit-bot: I haz the power, 2016-04-06 20:24:04]

Patchset 3 (id:??) landed as
https://crrev.com/e7680c79e7ebc47ffed579fe29c1bf574089999d
Cr-Commit-Position: refs/heads/master@{#385543}

[dcheng, 2016-04-06 23:12:21]

dcheng@chromium.org changed reviewers:
+ dcheng@chromium.org

[dcheng, 2016-04-06 23:12:22]

https://codereview.chromium.org/1826613003/diff/40001/remoting/host/security_...
File remoting/host/security_key/remote_security_key_main.cc (right):

https://codereview.chromium.org/1826613003/diff/40001/remoting/host/security_...
remoting/host/security_key/remote_security_key_main.cc:50:
scoped_ptr<RemoteSecurityKeyIpcClient> ipc_client(
Please don't forget to IWYU, this collided with
https://codereview.chromium.org/1864213002 and broke the build.

[joedow, 2016-04-06 23:16:42]

On 2016/04/06 23:12:22, dcheng wrote:
>
https://codereview.chromium.org/1826613003/diff/40001/remoting/host/security_...
> File remoting/host/security_key/remote_security_key_main.cc (right):
> 
>
https://codereview.chromium.org/1826613003/diff/40001/remoting/host/security_...
> remoting/host/security_key/remote_security_key_main.cc:50:
> scoped_ptr<RemoteSecurityKeyIpcClient> ipc_client(
> Please don't forget to IWYU, this collided with
> https://codereview.chromium.org/1864213002 and broke the build.

I seems like this patch landed ~2 hours before the referenced CL.  I'm happy to
update it with the changes from your CL.

[dcheng, 2016-04-06 23:18:07]

On 2016/04/06 at 23:16:42, joedow wrote:
> On 2016/04/06 23:12:22, dcheng wrote:
> >
https://codereview.chromium.org/1826613003/diff/40001/remoting/host/security_...
> > File remoting/host/security_key/remote_security_key_main.cc (right):
> > 
> >
https://codereview.chromium.org/1826613003/diff/40001/remoting/host/security_...
> > remoting/host/security_key/remote_security_key_main.cc:50:
> > scoped_ptr<RemoteSecurityKeyIpcClient> ipc_client(
> > Please don't forget to IWYU, this collided with
> > https://codereview.chromium.org/1864213002 and broke the build.
> 
> I seems like this patch landed ~2 hours before the referenced CL.  I'm happy
to update it with the changes from your CL.

Sure, the problem is the CQ run for the later patch didn't include this
particular revision, hence collision.