Add HostEventLogger to It2Me host plugin

Add HostEventLogger to It2Me host plugin


BUG=132886
TEST=Manual

[Lambros, 2012-07-19 01:31:17]

alexeypa: Please look at Windows changes to remoting.gyp - I don't have a Win
box to test this on, and I might not have done everything needed.
sergeyu: everything else

[alexeypa (please no reviews), 2012-07-19 17:05:00]

http://codereview.chromium.org/10673018/diff/1/remoting/host/plugin/host_scri...
File remoting/host/plugin/host_script_object.cc (right):

http://codereview.chromium.org/10673018/diff/1/remoting/host/plugin/host_scri...
remoting/host/plugin/host_script_object.cc:587: host_event_logger_ =
HostEventLogger::Create(host_, kApplicationName);
This is not going to work on Windows. Logging to the Event Log requires an event
source to be registered in the registry (per machine). For me2me host it is done
by the installer. it2me host on the other hand:

- Does not have admin privileges.
- Is installed per-user.

http://codereview.chromium.org/10673018/diff/1/remoting/remoting.gyp
File remoting/remoting.gyp (right):

http://codereview.chromium.org/10673018/diff/1/remoting/remoting.gyp#newcode1285
remoting/remoting.gyp:1285: 'host/remoting_host_messages.mc',
This should work, but it is a little bit tricky. The binaries including
remoting_host as a dependency will suddenly get the message table compiled from
remoting_host_messages.mc. The potential complications that I see are:

- There will be a comflict if a binary wants to use its own message table.
- The binary should be registered in the registry if it's message table is being
used to display messages in the Event Log.

[Lambros, 2012-07-19 23:05:04]

On 2012/07/19 17:05:00, alexeypa wrote:
>
http://codereview.chromium.org/10673018/diff/1/remoting/host/plugin/host_scri...
> File remoting/host/plugin/host_script_object.cc (right):
> 
>
http://codereview.chromium.org/10673018/diff/1/remoting/host/plugin/host_scri...
> remoting/host/plugin/host_script_object.cc:587: host_event_logger_ =
> HostEventLogger::Create(host_, kApplicationName);
> This is not going to work on Windows. Logging to the Event Log requires an
event
> source to be registered in the registry (per machine). For me2me host it is
done
> by the installer. it2me host on the other hand:
> 
> - Does not have admin privileges.
> - Is installed per-user.
> 
> http://codereview.chromium.org/10673018/diff/1/remoting/remoting.gyp
> File remoting/remoting.gyp (right):
> 
>
http://codereview.chromium.org/10673018/diff/1/remoting/remoting.gyp#newcode1285
> remoting/remoting.gyp:1285: 'host/remoting_host_messages.mc',
> This should work, but it is a little bit tricky. The binaries including
> remoting_host as a dependency will suddenly get the message table compiled
from
> remoting_host_messages.mc. The potential complications that I see are:
> 
> - There will be a comflict if a binary wants to use its own message table.
> - The binary should be registered in the registry if it's message table is
being
> used to display messages in the Event Log.

OK, I'll abandon this CL for now, as I can't do the Windows work we've
discussed.  Alexey, please feel free to start a new CL and incorporate whatever
changes you want from this CL.