Reporting of policy errors via host-offline-reason: part 2
commite26be729f1e985e47deb1dc1667c6c77c46872f6
authorlukasza <lukasza@chromium.org>
Wed, 26 Nov 2014 02:12:08 +0000 (25 18:12 -0800)
committerCommit bot <commit-bot@chromium.org>
Wed, 26 Nov 2014 02:12:39 +0000 (26 02:12 +0000)
treef95ba24963d65f3fab1375344eb9e8d656257543
parent94bcaa5665f9ffdb4455d7638cca83ad5941aefd
Reporting of policy errors via host-offline-reason: part 2

Removing host_status_sender.cc and moving this functionality into
heartbeat_sender.cc.  This avoids multiple issues related to
duplicated code and functionality:
- primarily, this enables sequence-id-based signatures (which are
  better than timestamp based signatures - they don't require the host
  and the bot to have synchronized clocks) without having to maintain
  a separate sequence id for host status messages.
- secondarily, this means we can avoid much code duplication (on the
  client side, but mostly on the server side)

Note that server side currently doesn't handle host-status messages
that are being removed by this changelist.

Handling of host-offline-reason attribute being added by this
changelist needs to be added to server side.  This is being tracked by
cr/78625042

BUG=410050

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

Cr-Commit-Position: refs/heads/master@{#305756}
remoting/host/heartbeat_sender.cc
remoting/host/heartbeat_sender.h
remoting/host/heartbeat_sender_unittest.cc
remoting/host/host_status_sender.cc [deleted file]
remoting/host/host_status_sender.h [deleted file]
remoting/host/host_status_sender_unittest.cc [deleted file]
remoting/host/remoting_me2me_host.cc
remoting/host/server_log_entry_host.cc
remoting/host/server_log_entry_host.h
remoting/remoting_host_srcs.gypi
remoting/remoting_test.gypi