Aavi@chromium.orgRevert 158366 - Cleanups in Chromoting Host.
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[Chromoting] Build Chromoting Host installation in two steps: (binaries & .wxs) -> .zip -> .msi. The two step process is needed so that we could take the produced .zip and use it to sign the binaries and installation on a separate machine. Decompiling .msi using dark proved to be a bad idea due to bugs in dark.exe. BUG=146863 Review URL: https://chromiumcodereview.appspot.com/10965013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157843 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Avoid potential conflicts leading to pending reboots while upgrading the me2me host: - Install the host binaries to versioned folders. - Drop references to the COM objects quickly. - Auto-generate CLSID of the daemon controller at GYP time. This makes sure that a freshly installed version of the controller will be launched after upgrade even if there is already running instance cached by RPCSS. This CL restores https://chromiumcodereview.appspot.com/10831037 (r148671) and https://chromiumcodereview.appspot.com/10837087 (r149866) previously reverted by r150494. Unlike the previous two CLs this one does not require GYP changes (that is changes to GYP itself, not .gyp files). BUG=137755 Review URL: https://chromiumcodereview.appspot.com/10828352 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152120 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Avoid potential conflicts leading to pending reboots while upgrading the me2me host: - Install the host binaries to versioned folders. - Drop references to the COM objects quickly. - Auto-generate CLSID of the daemon controller at GYP time. This makes sure that a freshly installed version of the controller will be launched after upgrade even if there is already running instance cached by RPCSS. This CL restores https://chromiumcodereview.appspot.com/10831037 (r148671) and https://chromiumcodereview.appspot.com/10837087 (r149866) previously reverted by r150494. Unlike the previous two CLs this one does not require GYP changes (that is changes to GYP itself, not .gyp files). BUG=137755 Review URL: https://chromiumcodereview.appspot.com/10828352 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152120 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] The daemon process now starts the networking process and passes the host configuration (and updates) over the IPC channel. This CL also switches to FilePathWatcher (to detect the configuration file changes) on all platforms. BUG=123696,134694 Review URL: https://chromiumcodereview.appspot.com/10855249 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154999 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Introducing refcount-based life time management of the message loops in the service (daemon) and me2me host (network) processes. This CL introduces AutoMessageLoop wrapper that provides control over life time of a message loop via scoped_refptr references. This scheme is useful in the cases when shutdown code has to run on a particular thread or when the OS requires resources (such as windows) to be freed before exiting a message loop. The CL switches threads, owned by remoting::HostService, remoting::HostProcess and remoting::ChromotingHostContext, to refcount-based lifetime management. This change required updating tear-down sequences in remoting_me2me_host and the host plugin code. BUG=134694 Review URL: https://chromiumcodereview.appspot.com/10829467 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154827 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Launch the host process elevated via ShellExecuteEx(). The host process is launched in in two steps now. An instance of remote_service.exe is launched in a user session (CreateProcessAsUser) and then it launches the host requesting elevation (ShellExecuteEx). This is needed because Windows 8 refuses to inject Alt+Tab unless uiAccess='true' is specified in the manifest, which in its turn requires ShellExecuteEx() to be used. Lifetime of launched processes is controlled by assigning them to a job object. Message loop changes are required to be able to process job object notifications on the I/O message loop. BUG=135217 Review URL: https://chromiumcodereview.appspot.com/10831271 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151973 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Launch the host process elevated via ShellExecuteEx(). The host process is launched in in two steps now. An instance of remote_service.exe is launched in a user session (CreateProcessAsUser) and then it launches the host requesting elevation (ShellExecuteEx). This is needed because Windows 8 refuses to inject Alt+Tab unless uiAccess='true' is specified in the manifest, which in its turn requires ShellExecuteEx() to be used. Lifetime of launched processes is controlled by assigning them to a job object. Message loop changes are required to be able to process job object notifications on the I/O message loop. BUG=135217 Review URL: https://chromiumcodereview.appspot.com/10831271 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151973 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Build Chromoting Host installation in two steps: (binaries & .wxs) -> .zip -> .msi. The two step process is needed so that we could take the produced .zip and use it to sign the binaries and installation on a separate machine. Decompiling .msi using dark proved to be a bad idea due to bugs in dark.exe. BUG=146863 Review URL: https://chromiumcodereview.appspot.com/10965013 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157843 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Adding the desktop integration binary to the host installation on Windows. The desktop integration binary is compiled and added to the host installation only when a multi-process host is built. This CL also renames a few constants to match the multi process host terminology more closely. BUG=134694 Review URL: https://chromiumcodereview.appspot.com/10910075 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156395 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Adding the desktop integration binary to the host installation on Windows. The desktop integration binary is compiled and added to the host installation only when a multi-process host is built. This CL also renames a few constants to match the multi process host terminology more closely. BUG=134694 Review URL: https://chromiumcodereview.appspot.com/10910075 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156395 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Refactoring DesktopEnvironment and moving screen/audio recorders to ClientSession. This CL changes the way screen/audio recorders and event executors are managed. New DesktopEnvironmentFactory class is now used by ChromotingHost's owner to specify the kind of desktop environment (or virtual terminal) to be used by the host. Screen/audio recorders and event executors now owned by the ClientSession instance, so there is a separate set of recorders and stubs exists for each authenticated client session. Clients sessions can now be torn dowsn in parallel with the host shuttting down. This is the 4th attempt to land this change. This version includes: - |ClientSession| objects are torn down asynchronously now. - |ClientSession| objects are ref-counted to facilitate the asynchronous shutdown. They still have to be used and destroyed on the network thread. - |ChromotingHost| now waits until all connections are torn down before deleting the session manager. - The unit tests were fixed to run message loops until all asynchronous object have been destroyed. - |ClientSessionTest.ClampMouseEvents| makes sure that the expectations are destroyed when leaving TEST_F scope so that ASAN is not getting confused. BUG=134694 TEST=remoting_unittests Review URL: https://chromiumcodereview.appspot.com/10916263 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156398 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Refactoring DesktopEnvironment and moving screen/audio recorders to ClientSession. This CL changes the way screen/audio recorders and event executors are managed. New DesktopEnvironmentFactory class is now used by ChromotingHost's owner to specify the kind of desktop environment (or virtual terminal) to be used by the host. Screen/audio recorders and event executors now owned by the ClientSession instance, so there is a separate set of recorders and stubs exists for each authenticated client session. Clients sessions can now be torn dowsn in parallel with the host shuttting down. This is the 4th attempt to land this change. This version includes: - |ClientSession| objects are torn down asynchronously now. - |ClientSession| objects are ref-counted to facilitate the asynchronous shutdown. They still have to be used and destroyed on the network thread. - |ChromotingHost| now waits until all connections are torn down before deleting the session manager. - The unit tests were fixed to run message loops until all asynchronous object have been destroyed. - |ClientSessionTest.ClampMouseEvents| makes sure that the expectations are destroyed when leaving TEST_F scope so that ASAN is not getting confused. BUG=134694 TEST=remoting_unittests Review URL: https://chromiumcodereview.appspot.com/10916263 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156398 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Refactoring DesktopEnvironment and moving screen/audio recorders to ClientSession. This CL changes the way screen/audio recorders and event executors are managed. New DesktopEnvironmentFactory class is now used by ChromotingHost's owner to specify the kind of desktop environment (or virtual terminal) to be used by the host. Screen/audio recorders and event executors now owned by the ClientSession instance, so there is a separate set of recorders and stubs exists for each authenticated client session. Clients sessions can now be torn dowsn in parallel with the host shuttting down. This is the 4th attempt to land this change. This version includes: - |ClientSession| objects are torn down asynchronously now. - |ClientSession| objects are ref-counted to facilitate the asynchronous shutdown. They still have to be used and destroyed on the network thread. - |ChromotingHost| now waits until all connections are torn down before deleting the session manager. - The unit tests were fixed to run message loops until all asynchronous object have been destroyed. - |ClientSessionTest.ClampMouseEvents| makes sure that the expectations are destroyed when leaving TEST_F scope so that ASAN is not getting confused. BUG=134694 TEST=remoting_unittests Review URL: https://chromiumcodereview.appspot.com/10916263 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156398 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Refactoring DesktopEnvironment and moving screen/audio recorders to ClientSession. This CL changes the way screen/audio recorders and event executors are managed. New DesktopEnvironmentFactory class is now used by ChromotingHost's owner to specify the kind of desktop environment (or virtual terminal) to be used by the host. Screen/audio recorders and event executors now owned by the ClientSession instance, so there is a separate set of recorders and stubs exists for each authenticated client session. Clients sessions can now be torn dowsn in parallel with the host shuttting down. This is the 4th attempt to land this change. This version includes: - |ClientSession| objects are torn down asynchronously now. - |ClientSession| objects are ref-counted to facilitate the asynchronous shutdown. They still have to be used and destroyed on the network thread. - |ChromotingHost| now waits until all connections are torn down before deleting the session manager. - The unit tests were fixed to run message loops until all asynchronous object have been destroyed. - |ClientSessionTest.ClampMouseEvents| makes sure that the expectations are destroyed when leaving TEST_F scope so that ASAN is not getting confused. BUG=134694 TEST=remoting_unittests Review URL: https://chromiumcodereview.appspot.com/10916263 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@156398 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] The daemon process now starts the networking process and passes the host configuration (and updates) over the IPC channel. This CL also switches to FilePathWatcher (to detect the configuration file changes) on all platforms. BUG=123696,134694 Review URL: https://chromiumcodereview.appspot.com/10855249 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154999 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] The daemon process now starts the networking process and passes the host configuration (and updates) over the IPC channel. This CL also switches to FilePathWatcher (to detect the configuration file changes) on all platforms. BUG=123696,134694 Review URL: https://chromiumcodereview.appspot.com/10855249 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154999 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Moving Windows-only files: remoting/host -> remoting/host/win. Review URL: https://chromiumcodereview.appspot.com/10832068 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149043 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
Revert 158366 - Cleanups in Chromoting Host. 1. Removed constants.[h|cc] 2. Removed platform if-defs in remoting_me2me_host.cc where they are not necessary. Review URL: https://codereview.chromium.org/10913260 TBR=sergeyu@chromium.org Review URL: https://codereview.chromium.org/10988004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@158400 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 | |
[Chromoting] Don't use a job object to control the me2me host process on Windows XP. The host binary specifies uiAccess='true' in its manifest that requires ShellExecute() to be used to launch it. Since ShellExecute() does not work across the session boundary we use a helper process to launch the me2me host. A job object is used to control both the helper process and the host process, so that they can be terminated if needed. Unfortunately, the helper process spawned by CreateRemoteSessionProcess() function cannot be assigned to a job object on Windows XP/2K3. This CL works it around by using two different kaunchers for XP and Vista+: - XP launches the host process directly using CreateRemoteSessionProcess(). uiAccess='true' is ignored on XP and ShellExecute() call is not necessary; - Vista+ used the helper process to launch the host and assigns boths processes to a job object. BUG=148781 Review URL: https://chromiumcodereview.appspot.com/10911267 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@157490 0039d316-1c4b-4281-b951-d872f2087c98 | 13 年前 |