summaryrefslogtreecommitdiffstats
path: root/remoting/remoting_host.gypi
Commit message (Collapse)AuthorAgeFilesLines
* CastExtension Impl for Chromoting Hostaiguha@chromium.org2014-08-161-1/+5
| | | | | | | | | | | | | | | Implements the HostExtension[Session] interfaces for WebRTC Peer Connection support in the Chromoting host. The CastExtension represents the "casting" capability of the Chromoting host. The CastExtensionSession encapsulates the WebRTC PeerConnection architecture needed to set up a peer connection with the client, using protocol::ExtensionMessages as the signaling channel for the connection. Review URL: https://codereview.chromium.org/399253002 Cr-Commit-Position: refs/heads/master@{#290129} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@290129 0039d316-1c4b-4281-b951-d872f2087c98
* I've created a new desktop environment, Me2MeWindowDesktopEnvironment. This ↵ronakvora@google.com2014-08-151-0/+6
| | | | | | | | | | | | | | environment has creates a WindowCapturerScreenWrapper instead of a ScreenCapturer with its CreateVideoCapturer() method. This wrapper wraps a WindowCapturer and delegates messages sent to it to the wrapped WindowCapturer. When the command line flag window-Id is specified the remoting_me2me_host.cc choses Me2MeWindowDesktopEnvironment instead of the regular desktop environment. Review URL: https://codereview.chromium.org/422503004 Cr-Commit-Position: refs/heads/master@{#289825} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289825 0039d316-1c4b-4281-b951-d872f2087c98
* Switch DesktopEnvironment to return a DesktopCapturer.wez@chromium.org2014-08-121-2/+2
| | | | | | | | | This removes the need for a lot of additional boilerplate in proxying capturer implementations, and makes it possible to implement DesktopEnvironment using any kind of DesktopCapturer, e.g. ScreenCapturer or WindowCapturer, for example. Review URL: https://codereview.chromium.org/455073004 Cr-Commit-Position: refs/heads/master@{#289020} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@289020 0039d316-1c4b-4281-b951-d872f2087c98
* CastVideoCapturerAdapter for WebRTC support in Chromotingaiguha@chromium.org2014-08-121-0/+4
| | | | | | | | | | | | | | | | | | | | | | | This class is an implementation of cricket::VideoCapturer, the core object used for video streaming in the WebRTC PeerConnection architecture. It acts as an adapter between conventional Chromoting screen capturing and the cricket::VideoCapturer interface. The CastVideoCapturerAdapter wraps a webrtc::ScreenCapturer object and captures frames at a pre-defined frame rate. Upon capture, it converts the received DesktopFrame to a cricket::CapturedFrame and fires SignalFrameCaptured() with it, at which point the base implementation takes over. This object can be used to construct one of type webrtc::VideoSourceInterface, which can be used to construct one of type webrtc::VideoTrackInterface, which can be added to a webrtc::MediaStreamInterface, which can be added to a webrtc::PeerConnection object. With that in place, we would be able to stream video to the other peer in the PeerConnection. Review URL: https://codereview.chromium.org/404443002 Cr-Commit-Position: refs/heads/master@{#288873} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@288873 0039d316-1c4b-4281-b951-d872f2087c98
* Use webrtc::MouseCursorMonitor for cursor shapesdcaiafa@chromium.org2014-08-081-0/+2
| | | | | | | | | | | | | | | | | | | | | Use webrtc::MouseCursorMonitor for cursor shapes instead of webrtc::VideoFrameCapturer, in preparation for deprecating cursor shape functionality in the latter. Fix memory corruption in VideoSchedulerTests_StartAndStop, where a lingering capture task could trigger a expectation action declared on the stack during tear down. My changes to the test somehow made the race condition more likely. BUG=324033 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=247689 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248045 Review URL: https://codereview.chromium.org/92473002 Cr-Commit-Position: refs/heads/master@{#288226} git-svn-id: svn://svn.chromium.org/chrome/trunk/src@288226 0039d316-1c4b-4281-b951-d872f2087c98
* webrtc deps in remoting should be inside a webrtc conditionmostynb@opera.com2014-08-021-2/+6
| | | | | | | | | | | | | | If you try to build with enable_webrtc=0 and remoting=1, gyp will fail: libjingle.gyp:libpeerconnection#target' when processing remoting.gyp:remoting_host#target. This happens because the libpeerconnnection target is defined inside an enable_webrtc==1 condition. Therefore, these dependencies in remoting.gyp should be too. BUG=399413 Review URL: https://codereview.chromium.org/431163002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287193 0039d316-1c4b-4281-b951-d872f2087c98
* Add video frame recording capability to Chromoting hosts.wez@chromium.org2014-08-021-0/+2
| | | | | | | | | | | | | | This will be used to record sequences of video frames for real-world sessions, for performance-evaluation purposes. If the host is run with a video-recording buffer size specified then it will advertise a videoRecorder capability to clients. Clients seeing this capability can send "video-recorder" extension messages to the host to start and stop recording, and to fetch the next recorded frame. Frames are encoded to VideoPackets using the "verbatim" encoder, and must then be serialized and Base-64 encoded for transmission via the extension message protocol. See crrev.com/386853002 for the client part of this. Review URL: https://codereview.chromium.org/372943002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@287183 0039d316-1c4b-4281-b951-d872f2087c98
* Add HostExtensionSessionManager to help ClientSession handle extensions.wez@chromium.org2014-07-311-0/+3
| | | | | | | | | | | | | | | | | This CL changes the HostExtension[Session] interface: 1. Each HostExtension may optionally specify one required capability; if the client does not offer the capability then the HostExtension is not instantiated for the session. 2. Each HostExtensionSession may optionally wrap or replace the video encoder or capturer for the session. 3. HostExtension[Session]s are passed the ClientSession's ClientSessionControl and ClientStub interfaces, rather than the concrete ClientSession class itself. 4. HostExtensionSessions may force the video pipeline to be re-created, if necessary. This will be used by the VideoFrameRecorder extension to allow it to wrap the VideoEncoder when it is first created. This CL also changes the host implementation and tests: 1. ChromotingHost passes the set of configured HostExtensions to each ClientSession to work with, rather than creating & applying HostExtensionSession instances directly. 2. All logic for managing HostExtension[Session]s is moved out of ClientSession into the new HostExtensionSessionManager sub-component. 3. The FakeExtension test implementation of HostExtension is moved out of the ClientSession unittests implementation, and updated to allow testing of e.g. encoder wrapping capabilities. Review URL: https://codereview.chromium.org/402233003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@286773 0039d316-1c4b-4281-b951-d872f2087c98
* Add disconnect_window.xib in the It2Me NM host bundle.sergeyu@chromium.org2014-07-261-0/+1
| | | | | | | | BUG=397261 Review URL: https://codereview.chromium.org/416333009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@285784 0039d316-1c4b-4281-b951-d872f2087c98
* Cast Port Allocator Factory for PeerConnectionaiguha@chromium.org2014-07-221-0/+3
| | | | | | | | | | This CL contains the implementation of PortAllocatorFactoryInterface in peerconnectioninterface.h. It bridges the gap in port allocation objects between WebRTC and Chromium. The factory produces a ChromiumPortAllocator that can successfully be used by the PeerConnection API. Review URL: https://codereview.chromium.org/398813003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@284589 0039d316-1c4b-4281-b951-d872f2087c98
* Cleanup list of source files in remoting targetssergeyu@chromium.org2014-07-171-3/+3
| | | | | | | | | | Some files were compiled for both remoting_host and remoting_core. Also moved some files to remoting_host so that they don't need to be listed multiple times for different platforms Review URL: https://codereview.chromium.org/393073002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@283597 0039d316-1c4b-4281-b951-d872f2087c98
* Pull out common code from client and host versions of LogToServerlambroslambrou@chromium.org2014-07-101-2/+2
| | | | | | | | | | Also added unittests for client code. TEST=unittests Review URL: https://codereview.chromium.org/320403002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@282193 0039d316-1c4b-4281-b951-d872f2087c98
* Move ServiceUrls to remoting/base.sergeyu@chromium.org2014-07-011-2/+0
| | | | | | | | | | ServiceUrls is also usable on the client side, particularly to get bot jid for logs. Moved to remoting/base where it can be reused by the client. Review URL: https://codereview.chromium.org/357503003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@280712 0039d316-1c4b-4281-b951-d872f2087c98
* Add VideoFrameRecorder for use recording test frame sequences.wez@chromium.org2014-06-271-0/+2
| | | | | | | | | | | | This will be used to record representative frame sequences for performance evaluation of the new VP9 encoder. BUG=260879 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=279795 Review URL: https://codereview.chromium.org/339073002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@280255 0039d316-1c4b-4281-b951-d872f2087c98
* Revert of Add VideoFrameRecorder for use recording test frame sequences. ↵avi@chromium.org2014-06-251-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (https://codereview.chromium.org/339073002/) Reason for revert: Brand new test fails in ASAN: Direct leak of 112 byte(s) in 1 object(s) allocated from: #0 0x462ccb in operator new(unsigned long) /usr/local/google/work/chromium/src/third_party/llvm/projects/compiler-rt/lib/asan/asan_new_delete.cc:55 #1 0x7ee8f9 in CreateNextFrame remoting/host/video_frame_recorder_unittest.cc:96 #2 0x7ee8f9 in remoting::VideoFrameRecorderTest::CreateTestFrames() remoting/host/video_frame_recorder_unittest.cc:112 #3 0x7f1184 in remoting::VideoFrameRecorderTest_EncodeButDontRecord_Test::TestBody() remoting/host/video_frame_recorder_unittest.cc:269 #4 0xb3bf38 in HandleExceptionsInMethodIfSupported<testing::Test, void> testing/gtest/src/gtest.cc:2045 #5 0xb3bf38 in testing::Test::Run() testing/gtest/src/gtest.cc:2061 #6 0xb3e1c9 in testing::TestInfo::Run() testing/gtest/src/gtest.cc:2237 #7 0xb3ef56 in testing::TestCase::Run() testing/gtest/src/gtest.cc:2344 #8 0xb5206a in testing::internal::UnitTestImpl::RunAllTests() testing/gtest/src/gtest.cc:4065 #9 0xb516a0 in HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool> testing/gtest/src/gtest.cc:2045 #10 0xb516a0 in testing::UnitTest::Run() testing/gtest/src/gtest.cc:3697 #11 0xab66bc in RUN_ALL_TESTS testing/gtest/include/gtest/gtest.h:2231 #12 0xab66bc in base::TestSuite::Run() base/test/test_suite.cc:227 #13 0xaada32 in Run base/callback.h:401 #14 0xaada32 in base::(anonymous namespace)::LaunchUnitTestsInternal(base::Callback<int ()> const&, int, bool, base::Callback<void ()> const&) base/test/launcher/unit_test_launcher.cc:498 #15 0xaad3ad in base::LaunchUnitTests(int, char**, base::Callback<int ()> const&) base/test/launcher/unit_test_launcher.cc:553 #16 0x4e8067 in main chrome/test/base/run_all_remoting_unittests.cc:31 #17 0x7f1f660df76c in __libc_start_main /build/buildd/eglibc-2.15/csu/libc-start.c:226 Original issue's description: > Add VideoFrameRecorder for use recording test frame sequences. > > This will be used to record representative frame sequences for performance evaluation of the new VP9 encoder. > > BUG=260879 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=279795 TBR=sergeyu@chromium.org,wez@chromium.org NOTREECHECKS=true NOTRY=true BUG=260879 Review URL: https://codereview.chromium.org/350903003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@279805 0039d316-1c4b-4281-b951-d872f2087c98
* Add VideoFrameRecorder for use recording test frame sequences.wez@chromium.org2014-06-251-0/+2
| | | | | | | | | | This will be used to record representative frame sequences for performance evaluation of the new VP9 encoder. BUG=260879 Review URL: https://codereview.chromium.org/339073002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@279795 0039d316-1c4b-4281-b951-d872f2087c98
* Remove NPAPI plugin from chromoting webapp.sergeyu@chromium.org2014-06-181-101/+0
| | | | | | | | | BUG=134215 R=weitaosu@chromium.org, wez@chromium.org Review URL: https://codereview.chromium.org/342583002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@278198 0039d316-1c4b-4281-b951-d872f2087c98
* TextEvent support on Linuxsergeyu@chromium.org2014-06-051-0/+2
| | | | | | | | BUG=270356 Review URL: https://codereview.chromium.org/307493002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@275052 0039d316-1c4b-4281-b951-d872f2087c98
* Host extensionsdcaiafa@chromium.org2014-05-301-1/+3
| | | | | | | | | | | | | | | | | | | | | This CL introduces HostExtension, an interface for classes that extend the host with non-core functionality. Extensions are added to the ChromotingHost. They are used to compile the list of capabilities reported to the client, which can be used by the client to determine the availability of the extension. When a client connects, a HostExtension has the opportunity to create an HostExtensionSession to hold client/extension state, and to handle extension messages from that client. BUG= NOTRY=true Review URL: https://codereview.chromium.org/301453003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@273901 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 273652 "Host extensions"mattm@chromium.org2014-05-301-2/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | gyp failure on Win: Exception: Missing input files: C:\b\build\slave\Win\build\src\remoting\host\extension.h C:\b\build\slave\Win\build\src\remoting\host\extension_session.h > Host extensions > > This CL introduces HostExtension, an interface for classes that > extend the host with non-core functionality. > > Extensions are added to the ChromotingHost. They are used to compile > the list of capabilities reported to the client, which can be used by > the client to determine the availability of the extension. > > When a client connects, a HostExtension has the opportunity to create > an HostExtensionSession to hold client/extension state, and to handle > extension messages from that client. > > BUG= > > Review URL: https://codereview.chromium.org/301453003 TBR=dcaiafa@chromium.org Review URL: https://codereview.chromium.org/308743006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@273674 0039d316-1c4b-4281-b951-d872f2087c98
* Host extensionsdcaiafa@chromium.org2014-05-291-0/+2
| | | | | | | | | | | | | | | | | | | This CL introduces HostExtension, an interface for classes that extend the host with non-core functionality. Extensions are added to the ChromotingHost. They are used to compile the list of capabilities reported to the client, which can be used by the client to determine the availability of the extension. When a client connects, a HostExtension has the opportunity to create an HostExtensionSession to hold client/extension state, and to handle extension messages from that client. BUG= Review URL: https://codereview.chromium.org/301453003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@273652 0039d316-1c4b-4281-b951-d872f2087c98
* Pull out common code from client and host versions of ServerLogEntry.lambroslambrou@chromium.org2014-05-221-2/+2
| | | | | | | | | | | | | | This also adds unittests for ServerLogEntry client code, with common code pulled out to a separate file. This doesn't affect LogToServer classes - they will be refactored in a separate CL. Also fix some IWYU issues uncovered by the refactor. TEST=unittests Review URL: https://codereview.chromium.org/282063005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@272346 0039d316-1c4b-4281-b951-d872f2087c98
* Remove {linux|android}_use_tcmalloc and switch to use_allocator in Chromium.dmikurube@chromium.org2014-05-071-6/+3
| | | | | | | | | | | | | | If this change breaks some bots, please try restarting the bot before reverting it. http://crrev.com/264460 may not be effective yet until restarting. See the bug and http://crrev.com/255129 for the details. BUG=345554 Review URL: https://codereview.chromium.org/258433005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@268876 0039d316-1c4b-4281-b951-d872f2087c98
* Pull the me2me host and prefpane bundle names from branding_chrom*.weitaosu@chromium.org2014-03-311-1/+7
| | | | | | | | BUG= Review URL: https://codereview.chromium.org/210093006 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@260706 0039d316-1c4b-4281-b951-d872f2087c98
* Fix remoting dependency.avi@chromium.org2014-03-301-0/+1
| | | | | | | | | BUG=357715 TEST=none Review URL: https://codereview.chromium.org/217133007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@260462 0039d316-1c4b-4281-b951-d872f2087c98
* Add breakpad support for me2me and it2me native messaging host on Mac.weitaosu@chromium.org2014-03-281-3/+130
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes in this CL include: 1. Initialize breakpad in it2me native messaging host 2. Create bundles for it2me and me2me native messaging hosts and move them out of the me2me host bundle (and update the manifests accordingly). 3. Dump symbols of the it2me and me2me native messaging hosts 4. Sign the me2me and it2me native messaging hosts 4. Rename the me2me host bundle and the prefPane bundle to get rid of the internal chromium/chromoting names and to conform to Mac convention 5. Refactor GYP, build-installer-archive.py, and do_signing.sh, etc to use name constants from branding_chrome and branding_chromium instead of hard coded names. This ensures that all the name constants are defined in a central location and reduces duplicate name definitions. Here are the names of the host bundles: me2me host: old name: org.chromium.chromoting.me2me_host new name: ChromeRemoteDesktop.Host Pref pane: old name: org.chromium.chromoting.prefPane new name: ChromeRemoteDesktop.prefPane it2me nm host: name: NativeMessagingHost Full Path: /Library/Google/ChromeRemoteDesktop/NativeMessagingHost.app me2me nm host: name: RemoteAssistanceHost Full path: /Library/Google/ChromeRemoteDesktop/RemoteAssistanceHost.app BUG= Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=259287 Review URL: https://codereview.chromium.org/186763004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@260075 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 259287 "Add breakpad support for me2me and it2me native m..."ernstm@chromium.org2014-03-251-130/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Breaks Google Chrome build: http://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Linux%20x64/builds/49089/steps/compile/logs/stdio > Add breakpad support for me2me and it2me native messaging host on Mac. > > Changes in this CL include: > 1. Initialize breakpad in it2me native messaging host > 2. Create bundles for it2me and me2me native messaging hosts and move them out of the me2me host bundle (and update the manifests accordingly). > 3. Dump symbols of the it2me and me2me native messaging hosts > 4. Sign the me2me and it2me native messaging hosts > 4. Rename the me2me host bundle and the prefPane bundle to get rid of the internal chromium/chromoting names and to conform to Mac convention > 5. Refactor GYP, build-installer-archive.py, and do_signing.sh, etc to use name constants from branding_chrome and branding_chromium instead of hard coded names. This ensures that all the name constants are defined in a central location and reduces duplicate name definitions. > > Here are the names of the host bundles: > > me2me host: > old name: org.chromium.chromoting.me2me_host > new name: ChromeRemoteDesktop.Host > > Pref pane: > old name: org.chromium.chromoting.prefPane > new name: ChromeRemoteDesktop.prefPane > > it2me nm host: > name: NativeMessagingHost > Full Path: /Library/Google/ChromeRemoteDesktop/NativeMessagingHost.app > > me2me nm host: > name: RemoteAssistanceHost > Full path: /Library/Google/ChromeRemoteDesktop/RemoteAssistanceHost.app > > BUG= > > Review URL: https://codereview.chromium.org/186763004 TBR=weitaosu@chromium.org Review URL: https://codereview.chromium.org/209043004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@259400 0039d316-1c4b-4281-b951-d872f2087c98
* Add breakpad support for me2me and it2me native messaging host on Mac.weitaosu@chromium.org2014-03-251-3/+130
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Changes in this CL include: 1. Initialize breakpad in it2me native messaging host 2. Create bundles for it2me and me2me native messaging hosts and move them out of the me2me host bundle (and update the manifests accordingly). 3. Dump symbols of the it2me and me2me native messaging hosts 4. Sign the me2me and it2me native messaging hosts 4. Rename the me2me host bundle and the prefPane bundle to get rid of the internal chromium/chromoting names and to conform to Mac convention 5. Refactor GYP, build-installer-archive.py, and do_signing.sh, etc to use name constants from branding_chrome and branding_chromium instead of hard coded names. This ensures that all the name constants are defined in a central location and reduces duplicate name definitions. Here are the names of the host bundles: me2me host: old name: org.chromium.chromoting.me2me_host new name: ChromeRemoteDesktop.Host Pref pane: old name: org.chromium.chromoting.prefPane new name: ChromeRemoteDesktop.prefPane it2me nm host: name: NativeMessagingHost Full Path: /Library/Google/ChromeRemoteDesktop/NativeMessagingHost.app me2me nm host: name: RemoteAssistanceHost Full path: /Library/Google/ChromeRemoteDesktop/RemoteAssistanceHost.app BUG= Review URL: https://codereview.chromium.org/186763004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@259287 0039d316-1c4b-4281-b951-d872f2087c98
* Do minimal processing of gnubby data. Add request timeouts and send errorpsj@chromium.org2014-03-241-2/+2
| | | | | | | | | | | | responses as necessary. Requires gnubbyd 0.8.37 or later. BUG=134250 Review URL: https://codereview.chromium.org/205493005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@258844 0039d316-1c4b-4281-b951-d872f2087c98
* Remove RULE_INPUT_PATH from inputs.garykac@chromium.org2014-03-171-3/+0
| | | | | | | | | | | | | These inputs are not necessary because RULE_INPUT_PATH is always an input of a rule. And the .gyp spec doesn't guarantee that the RULE_INPUT_* variables exist for the inputs list. BUG= R=sergeyu@chromium.org Review URL: https://codereview.chromium.org/197233010 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@257511 0039d316-1c4b-4281-b951-d872f2087c98
* Add use_allocator instead of linux_use_tcmalloc to switch the allocator.dmikurube@chromium.org2014-03-051-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change is to add a new build option 'use_allocator' which will replace 'linux_use_tcmalloc' in the future. It doesn't change the behavior immediately. The migration plan is as follows: 1) (this change) ... Add 'use_allocator' and set its default to "see_use_tcmalloc". ... Change allocator conditions to check use_allocator firstly. ... Use linux_use_tcmalloc if use_allocator=="see_use_tcmalloc". ... NO IMPACT without specifying use_allocator explicitly. 2) Change Blink to accept use_allocator. http://crrev.com/177053003/ 3) Change gyp to accept use_allocator. http://crrev.com/178643004/ 4) PSA the transition period to chromium-dev@. 5) (after the PSA-ed transition period) ... Make 'use_allocator' to "tcmalloc" or "none" (it depends) by default. ... Remove all linux_use_tcmalloc. ... Assert in gyp_chromium to check if linux_use_tcmalloc is not specified. At the point of this change (1), linux_use_tcmalloc is still used by default because 'use_allocator%': "see_use_tcmalloc". As written in http://crbug.com/345554, linux_use_tcmalloc would be confusing to have more options about allocators. We plan to: A) enable gperftools' heap-profiler with non-tcmalloc allocator, B) add a new memory allocator instead of tcmalloc. BUG=345554, 339604, 341349 R=agl@chromium.org, brettw@chromium.org, dgarrett@chromium.org, jam@chromium.org, jamesr@chromium.org, joi@chromium.org, miket@chromium.org, nick@chromium.org, rsleevi@chromium.org, scherkus@chromium.org, sergeyu@chromium.org, shess@chromium.org, sievers@chromium.org, sky@chromium.org, vitalybuka@chromium.org, willchan@chromium.org Review URL: https://codereview.chromium.org/177353002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255129 0039d316-1c4b-4281-b951-d872f2087c98
* Move it2me native messaging host implementation to remoting_core on windows.weitaosu@chromium.org2014-02-261-57/+32
| | | | | | | | | | | This will reduce the size of remote_assistance_host.exe and thus the host download. The size of the debug binary went down from 22MB to 440KB. BUG=309844 Review URL: https://codereview.chromium.org/178473002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253446 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor TokenValidatorImpl into a base class + implementation.rmsousa@chromium.org2014-02-261-0/+2
| | | | | | | | | | Most of the common logic and response handling code are moved into a base class, and the implementation contains just the logic to prepare the validation request (which is where the actual keypair-based authentication happens). This makes it easier to implement different, non-keypair-based host authentication mechanisms. BUG= Review URL: https://codereview.chromium.org/165293004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253378 0039d316-1c4b-4281-b951-d872f2087c98
* Moving me2me native messaging host implementation to remoting_core on Windows. weitaosu@chromium.org2014-02-251-40/+26
| | | | | | | | | | This significantly reduces the size of remoting_native_messaging_host.exe and thus the download size of the Windows host package. The size of the debug binary was reduced to 440k from 17M. BUG=325567 Review URL: https://codereview.chromium.org/166203003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253186 0039d316-1c4b-4281-b951-d872f2087c98
* [Chromoting] Fix alpha order of host files.garykac@chromium.org2014-02-251-1/+1
| | | | | | | | BUG= Review URL: https://codereview.chromium.org/166263003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@253152 0039d316-1c4b-4281-b951-d872f2087c98
* Add gnubby authentication to remoting hostpsj@chromium.org2014-02-201-0/+6
| | | | | | | | | | | | The remoting host changes, including the associated policy definitions, required to proxy gnubby traffic through a Chrome Remote Desktop session. BUG=134250 Review URL: https://codereview.chromium.org/138753005 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@252217 0039d316-1c4b-4281-b951-d872f2087c98
* Add version info resource to the it2me and me2me native messaging hosts.weitaosu@chromium.org2014-02-191-0/+26
| | | | | | | | BUG=338952,325567 Review URL: https://codereview.chromium.org/171163003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251921 0039d316-1c4b-4281-b951-d872f2087c98
* Add the it2me native messaging host to the windows installer.weitaosu@chromium.org2014-02-151-1/+2
| | | | | | | | BUG=338952 Review URL: https://codereview.chromium.org/168113002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251560 0039d316-1c4b-4281-b951-d872f2087c98
* Add missing remoting_host dependency on remoting_lib_idl.wez@chromium.org2014-02-151-0/+1
| | | | | | | | | remoting_lib_idl generates chromoting_lib.h from IDL, which the DesktopSessionWin implemenation in remoting_host depends upon. Review URL: https://codereview.chromium.org/165683002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251556 0039d316-1c4b-4281-b951-d872f2087c98
* Enable pairing registry in me2me native messaging host on Windows:weitaosu@chromium.org2014-02-131-23/+23
| | | | | | | | | | | | | | | | 1. Build a standalone remoting_native_messaging_host.exe. remoting_host.exe is a win32 application (as opposed to console application) thus not suitable as a native messaging host. 2. Initialize the pairing registry reg keys in the native messaging host. 3. GetPairdClients doesn't require elevation. 4. Add the native messaging host binary and manifest and the pairing reg keys to the installer. Enable pairing registry in Me2Me native messaging host on Windows. BUG=325567 Review URL: https://codereview.chromium.org/143303007 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@251137 0039d316-1c4b-4281-b951-d872f2087c98
* Separate access token caching logic from signaling connector.rmsousa@chromium.org2014-02-111-0/+2
| | | | | | | | | | Right now signaling connector is the only user of OAuth tokens, but if/when we add more authenticated calls, this will allow them to share the cached access token (so that consecutive authenticated calls from different objects don't need to make separate refreshtoken calls). BUG= Review URL: https://codereview.chromium.org/141063009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@250351 0039d316-1c4b-4281-b951-d872f2087c98
* Enable per-monitor DPI Awareness for Me2Me and It2me native messaging.rmsousa@chromium.org2014-02-061-0/+1
| | | | | | | | | | | The "true/pm" value is processed correctly on Win8.1 (per-monitor aware), and on previous versions (system dpi aware). See http://msdn.microsoft.com/en-us/library/windows/desktop/dn469266(v=vs.85).aspx#supporting_dynamic_dpi_changes for details. BUG=329343 Review URL: https://codereview.chromium.org/147993008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@249337 0039d316-1c4b-4281-b951-d872f2087c98
* Use gyp targets to link in X11 libraries instead of setting -lXfoojamesr@chromium.org2014-02-051-6/+6
| | | | | | | | | | | | | | This sets up gyp targets for the various X11 libraries we use and uses pkg-config to determine the correct cflags/ldflags incantations to use to link against them instead of listing out -lXfoo lines in libraries sections in gyp targets throughout the tree. This is more likely to generate the right lines and makes the dependencies a bit more explicit. BUG=339518 Review URL: https://codereview.chromium.org/153223002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248939 0039d316-1c4b-4281-b951-d872f2087c98
* Use correct path for remote_assistance_hostsergeyu@chromium.org2014-02-031-1/+1
| | | | | | | | BUG=309844 Review URL: https://codereview.chromium.org/147273003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248607 0039d316-1c4b-4281-b951-d872f2087c98
* It2me native messaging host: webapp implementation.weitaosu@chromium.org2014-02-021-0/+22
| | | | | | | | | | | | | | | | | | The webapp implementation of the it2me native messaging is based on the me2me couterpart. But I got rid of the per-message onDone/onError callbacks because unlike me2me, all requests to the it2me host are asynchronous: direct responses to all requests are meaningless. Only the asynchronous callbacks on host state change and nat policy update need to be processed. I verified that this is fully functional on Linux. Windows and Mac verification haven't been done and are planned after the linux work is completed. BUG=309844 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248072 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248157 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248255 Review URL: https://codereview.chromium.org/138503009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248391 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 248255 "It2me native messaging host: webapp implementation."avi@chromium.org2014-01-311-21/+0
| | | | | | | | | | | | | | | | | | | | | | | | This broke the official Mac builder. See the details in the original CL. > It2me native messaging host: webapp implementation. > > The webapp implementation of the it2me native messaging is based on the me2me couterpart. But I got rid of the per-message onDone/onError callbacks because unlike me2me, all requests to the it2me host are asynchronous: direct responses to all requests are meaningless. Only the asynchronous callbacks on host state change and nat policy update need to be processed. > > I verified that this is fully functional on Linux. Windows and Mac verification haven't been done and are planned after the linux work is completed. > > BUG=309844 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248072 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248157 > > Review URL: https://codereview.chromium.org/138503009 TBR=weitaosu@chromium.org Review URL: https://codereview.chromium.org/143883015 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248281 0039d316-1c4b-4281-b951-d872f2087c98
* It2me native messaging host: webapp implementation.weitaosu@chromium.org2014-01-311-0/+21
| | | | | | | | | | | | | | | | The webapp implementation of the it2me native messaging is based on the me2me couterpart. But I got rid of the per-message onDone/onError callbacks because unlike me2me, all requests to the it2me host are asynchronous: direct responses to all requests are meaningless. Only the asynchronous callbacks on host state change and nat policy update need to be processed. I verified that this is fully functional on Linux. Windows and Mac verification haven't been done and are planned after the linux work is completed. BUG=309844 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248072 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248157 Review URL: https://codereview.chromium.org/138503009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248255 0039d316-1c4b-4281-b951-d872f2087c98
* Revert of It2me native messaging host: webapp implementation. ↵caseq@chromium.org2014-01-311-21/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (https://codereview.chromium.org/138503009/) Reason for revert: Broke mac build again: http://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Mac/builds/16217 Original issue's description: > It2me native messaging host: webapp implementation. > > The webapp implementation of the it2me native messaging is based on the me2me couterpart. But I got rid of the per-message onDone/onError callbacks because unlike me2me, all requests to the it2me host are asynchronous: direct responses to all requests are meaningless. Only the asynchronous callbacks on host state change and nat policy update need to be processed. > > I verified that this is fully functional on Linux. Windows and Mac verification haven't been done and are planned after the linux work is completed. > > BUG=309844 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248072 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248157 TBR=jamiewalch@chromium.org,lambroslambrou@chromium.org,sergeyu@chromium.org,weitaosu@chromium.org NOTREECHECKS=true NOTRY=true BUG=309844 Review URL: https://codereview.chromium.org/150983004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248168 0039d316-1c4b-4281-b951-d872f2087c98
* It2me native messaging host: webapp implementation.weitaosu@chromium.org2014-01-311-0/+21
| | | | | | | | | | | | | | The webapp implementation of the it2me native messaging is based on the me2me couterpart. But I got rid of the per-message onDone/onError callbacks because unlike me2me, all requests to the it2me host are asynchronous: direct responses to all requests are meaningless. Only the asynchronous callbacks on host state change and nat policy update need to be processed. I verified that this is fully functional on Linux. Windows and Mac verification haven't been done and are planned after the linux work is completed. BUG=309844 Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=248072 Review URL: https://codereview.chromium.org/138503009 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248157 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 248045 "Use webrtc::MouseCursorMonitor for cursor shapes"benwells@chromium.org2014-01-311-2/+0
| | | | | | | | | | | | | | | | | | | | | > Use webrtc::MouseCursorMonitor for cursor shapes > > Use webrtc::MouseCursorMonitor for cursor shapes instead of > webrtc::VideoFrameCapturer, in preparation for deprecating cursor shape > functionality in the latter. > > BUG=324033 > > Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=247689 > > Review URL: https://codereview.chromium.org/92473002 This caused errors on a windows memory bot. See bug for details. TBR=dcaiafa@chromium.org Review URL: https://codereview.chromium.org/151163002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@248139 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-19 11:00:10 +0000