Improve IT2Me error logging.
commite12933bc63b336c98e60024a70220b1995463a96
authorjamiewalch <jamiewalch@chromium.org>
Tue, 30 Jun 2015 01:19:11 +0000 (29 18:19 -0700)
committerCommit bot <commit-bot@chromium.org>
Tue, 30 Jun 2015 01:19:45 +0000 (30 01:19 +0000)
tree04c1118025f41e223dec1f939465daf69b61498c
parent17a6f50d17ba4f6f8ae067691097f22315d0518c
Improve IT2Me error logging.

When a host is unable to set-up sharing for IT2Me, there is currently no
reportable error message (with the exception of failure due to domain
policy). This CL adds an error message to the native messaging protocol,
logging it to the console. In the longer term, as we identify common
failures, it makes sense to treat them like we do kInvalidDomainError,
and show a proper error message, but for now this will help us track
down what the common failures are.

As part of cleaning this up, I've deprecated web-app support for errors
being reported as a host state change message. These were being handled
the same way as the top-level "error" message, and the latter has the
advantage of not being tied to a host state change.

BUG=505627

Review URL: https://codereview.chromium.org/1216743005

Cr-Commit-Position: refs/heads/master@{#336706}
remoting/host/it2me/it2me_host.cc
remoting/host/it2me/it2me_host.h
remoting/host/it2me/it2me_native_messaging_host.cc
remoting/host/it2me/it2me_native_messaging_host.h
remoting/host/it2me/it2me_native_messaging_host_unittest.cc
remoting/host/register_support_host_request.cc
remoting/host/register_support_host_request.h
remoting/host/register_support_host_request_unittest.cc
remoting/webapp/crd/js/host_screen.js
remoting/webapp/crd/js/it2me_host_facade.js