Log when the host is started for an account.

remoting/host/host_event_logger.h

Index: remoting/host/host_event_logger.h
diff --git a/remoting/host/host_event_logger.h b/remoting/host/host_event_logger.h
index b039b3b5e50d9ffe634e3cb1a62dc4043c68ffea..3b5ced18d5e49e855bf470631e543ae3e8119490 100644
--- a/remoting/host/host_event_logger.h
+++ b/remoting/host/host_event_logger.h
@@ -24,6 +24,8 @@ class HostEventLogger {
   static scoped_ptr<HostEventLogger> Create(
       ChromotingHost* host, const std::string& application_name);
 
+  // Called when hosting is started for an account.
+  virtual void OnStart(const std::string& xmpp_login) {};

[alexeypa (please no reviews), 2012/08/29 15:15:48]

ChromotingHost::Start is called after HostEventLogger is created. I think it is
better to add OnStart to HostStatusObserver and pass uid to ChromotigHost::Start
which in its turn will pass it to HostStatusObserver::OnStart.

[Jamie, 2012/08/29 17:24:14]

I agree. HostStatusObserver is the best place to add callbacks of this nature,
assuming the plumbing to get the relevant information to the call site is not
too painful.

[Lambros, 2012/08/29 17:34:25]

nit: no semicolon needed

[rmsousa, 2012/08/29 19:24:40]

Done.

[rmsousa, 2012/08/29 19:24:40]

Done.

[rmsousa, 2012/08/29 19:24:40]

Done.

  protected:
   HostEventLogger() {}