summaryrefslogtreecommitdiffstats
path: root/remoting/client/chromoting_client.cc
Commit message (Collapse)AuthorAgeFilesLines
* Call SetViewport when client is inite'edgarykac@chromium.org2010-10-131-0/+1
| | | | | | | | | BUG=none TEST=run chromoting host/client, verify it works Review URL: http://codereview.chromium.org/3709004 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@62459 0039d316-1c4b-4281-b951-d872f2087c98
* Hook up communication between Chromoting plugin and JS so that it can notify ↵garykac@chromium.org2010-10-081-26/+6
| | | | | | | | | | | | | the JS UI of status changes. Push SetState handling down ChromotingView so that UI changes are contained in the View. BUG=54855 TEST=chromoting unittests Review URL: http://codereview.chromium.org/3446020 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61977 0039d316-1c4b-4281-b951-d872f2087c98
* Use new Chromotocol code in host andclient.sergeyu@chromium.org2010-10-061-8/+8
| | | | | | | | | | | | | | 1. ProtocolDecoder renamed to MessagesDecoder and moved to remoting/protocol. 2. base/protocol_util.[h|cc] split into base/util.[h|cc] and protocol/util.[h|cc]. 3. Added StreamReader and StreamWriter classes for events and video channels. 4. Client and host changed to use the new protocol code. BUG=None TEST=Unittests Review URL: http://codereview.chromium.org/3595012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61723 0039d316-1c4b-4281-b951-d872f2087c98
* This is a monster CL.ajwong@chromium.org2010-10-041-44/+75
| | | | | | | | | | | | | | | | | | | | It started as an attempt to put the decoder onto another thread. However, this became complicated due to multiple object ownership transfers and coupling between the decode layer and the network layer; the decoder's states were highly coupled with how the network packets were processed. This could probably be broken up slightly, but at this point, it's easier to just commit as a whole The refactor includes: 1) Making the decoder interface unaware of "network packet" types. 2) Making the network layer process packets in order. 3) Threading through asynchronous APIs all over the place. 4) Simplifying the rectangle update protocol. 5) Cleaning up object lifetime and ownership semantics between the decode layer and the renderer. As of right now, the Verbatim format is still broken on the encode side because it uses the old protocol. BUG=52883, 57351 TEST=still connects to chromoting_simple_host Review URL: http://codereview.chromium.org/3305001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@61402 0039d316-1c4b-4281-b951-d872f2087c98
* Jingle_glue bugfixes.sergeyu@chromium.org2010-08-281-3/+0
| | | | | | | | | | | | | | | Fixed Closed() methods in JingleChannel and JingleClient so that they are not blocking and guarantee that callback is not called afterwards. Changed JingleThread shutdown mechanism so that the thread doesn't stop until all tasks are finished. JingleClient now uses LocalTunnelSessionClient that allows local connections. BUG=52889 TEST=unittests Review URL: http://codereview.chromium.org/3167047 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57770 0039d316-1c4b-4281-b951-d872f2087c98
* Rename (Host|Client)Message to Chromoting(Host|Client)Message.garykac@chromium.org2010-08-241-6/+6
| | | | | | | | | | | | | | | | Rename HostMessage and ClientMessage to Chromoting{Host|Client}Message to avoid conflicts with messages in X11. Actually, only ClientMessage needs to be changed due to conflict, but HostMessage is changed to keep the names consistent. BUG=none TEST=remoting unittests Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=57112 Review URL: http://codereview.chromium.org/3161034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57255 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 57112 - Rename (Host|Client)Message to Chromoting(Host|Client)Message.thestig@chromium.org2010-08-231-6/+6
| | | | | | | | | | | | | | | | | Rename HostMessage and ClientMessage to Chromoting{Host|Client}Message to avoid conflicts with messages in X11. Actually, only ClientMessage needs to be changed due to conflict, but HostMessage is changed to keep the names consistent. BUG=none TEST=remoting unittests Review URL: http://codereview.chromium.org/3161034 TBR=garykac@chromium.org Review URL: http://codereview.chromium.org/3141036 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57115 0039d316-1c4b-4281-b951-d872f2087c98
* Rename (Host|Client)Message to Chromoting(Host|Client)Message.garykac@chromium.org2010-08-231-6/+6
| | | | | | | | | | | | | | Rename HostMessage and ClientMessage to Chromoting{Host|Client}Message to avoid conflicts with messages in X11. Actually, only ClientMessage needs to be changed due to conflict, but HostMessage is changed to keep the names consistent. BUG=none TEST=remoting unittests Review URL: http://codereview.chromium.org/3161034 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@57112 0039d316-1c4b-4281-b951-d872f2087c98
* Change ClientConfig to be a struct since it's just a dumb data carrier.ajwong@chromium.org2010-07-271-2/+1
| | | | | | | Also, the old method of passing around a pointer was not safe due to object lifetime issues. git-svn-id: svn://svn.chromium.org/chrome/trunk/src@53851 0039d316-1c4b-4281-b951-d872f2087c98
* Refactor the client code for the X11 version.garykac@google.com2010-07-201-52/+98
| | | | | | | | | | | | | Make ChromotingViews responsible for initializing themselves. Move all x11-related code into X11View. Create InputCapturer class manage client input capture. BUG=none TEST=ran Win host + X11 client Review URL: http://codereview.chromium.org/2861047 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@52973 0039d316-1c4b-4281-b951-d872f2087c98
* Reapply r51857 to start building chromoting plugin. Update for ppapi changes.ajwong@chromium.org2010-07-161-5/+5
| | | | | | | | | | | | | | This should work now after the ppapi roll to r164 that fixes the -fvisibility=hidden being removed in the linux shlib build. Original Review here: http://codereview.chromium.org/2858037 BUG=none TEST=try bots + local run of PPAPITest with a shared_library build. Review URL: http://codereview.chromium.org/3038001 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@52658 0039d316-1c4b-4281-b951-d872f2087c98
* Revert r51857 "Integrating back into using the external ppapi/cpp wrappers."ajwong@chromium.org2010-07-081-5/+5
| | | | | | | | For some reason, this looks like it breaks all PPAPI ui tests on linux. TBR: tonyg git-svn-id: svn://svn.chromium.org/chrome/trunk/src@51885 0039d316-1c4b-4281-b951-d872f2087c98
* Integrating back into using the external ppapi/cpp wrappers.ajwong@chromium.org2010-07-081-5/+5
| | | | | | | | | | | This should bring us close to Gary's original npapi code. BUG=none TEST=can connect to simple host Review URL: http://codereview.chromium.org/2858037 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@51857 0039d316-1c4b-4281-b951-d872f2087c98
* Hookup the ChromotingPlugin into the refactored implementationajwong@chromium.org2010-06-171-0/+170
of HostConnection and ChromotingView. Also implement a bare-bones PepperView. No unittests yet. Still too in flux to be worth it. BUG=none TEST=none Review URL: http://codereview.chromium.org/2852003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@50116 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-28 20:31:06 +0000