Merged all Chromoting Host code into remoting_core.dll (Windows).

remoting/branding_Chrome

Index: remoting/branding_Chrome
diff --git a/remoting/branding_Chrome b/remoting/branding_Chrome
index 028c3d20a28b343d84903c73321269598cbd8305..e1996684beb12908b252c05c5e4793f0e9e0f64e 100644
--- a/remoting/branding_Chrome
+++ b/remoting/branding_Chrome
@@ -9,6 +9,7 @@ DAEMON_FILE_NAME=Chrome Remote Desktop Host Service
 DAEMON_DESCRIPTION=Chrome Remote Desktop Host Service
 CONTROLLER_DESCRIPTION=Chrome Remote Desktop Host Controller
 DESKTOP_DESCRIPTION=Chrome Remote Desktop Integration Process
+CORE_DESCRIPTION=Chrome Remote Desktop Core

[Sergey Ulanov, 2013/01/18 21:14:55]

Maybe "Chrome Remote Desktop Host Core"?

[alexeypa (please no reviews), 2013/01/18 22:06:10]

While writing the multi-process specification I encountered the problem that we
call two different thigh "Chromoting Host":
1. The whole me2me host that includes everything that gets installed on the host
machine, except the webapp.
2. The host code handling incoming connections, capturing screen, etc.

It becomes very confusing so I'm trying to avoid using "host" for anything that
is not #2 from above.

Now, I realize that remoting_core.dll will have all host's code. But it will
also have other code, co by the argument above it is again desirable to avoid
calling it "host".

[Sergey Ulanov, 2013/01/24 20:02:11]

Well, we still need some name for (1). Maybe call it "Chrome Remote Desktop Host
Service Core"?

[alexeypa (please no reviews), 2013/01/28 21:57:29]

"Core" is not (1). remoting_core.dll is just a container for code of other
components. It does not have a role of it's own, so I don't think naming it by
its role is going to work. "Core" is generic and meaning-less enough that it
might work. It could be just "remoting.dll" as well.

 MAC_BUNDLE_ID=com.google.Chrome
 MAC_CREATOR=rimZ
 MAC_HOST_BUNDLE_ID=com.google.chrome_remote_desktop.remoting_me2me_host