Log when the host is started for an account.

remoting/host/host_event_logger.h

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef REMOTING_HOST_HOST_EVENT_LOGGER_H_
 #define REMOTING_HOST_HOST_EVENT_LOGGER_H_
 
 #include <string>
 
 #include "base/basictypes.h"
 #include "base/compiler_specific.h"
 #include "base/memory/scoped_ptr.h"
 
 namespace remoting {
 
 class ChromotingHost;
 
 class HostEventLogger {
  public:
   virtual ~HostEventLogger() {}
 
   // Creates an event-logger that monitors host status changes and logs
   // corresponding events to the OS-specific log (syslog/EventLog).
   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() {}
 
  private:
   DISALLOW_COPY_AND_ASSIGN(HostEventLogger);
 };
 
 }
 
 #endif  // REMOTING_HOST_HOST_EVENT_LOGGER_H_