1. 22 Jul, 2016 1 commit
  2. 06 Apr, 2016 1 commit
  3. 19 Jan, 2016 1 commit
  4. 05 Jan, 2016 1 commit
  5. 22 Dec, 2015 1 commit
  6. 20 Aug, 2015 1 commit
    • sergeyu's avatar
      remoting: Simplify FrameConsumer interface and remove FrameProducer interface. · 13bca69c
      sergeyu authored
      Now FrameConsumer implementation is responsible for scaling. This makes
      interaction with FrameConsumer much simpler. Also removed FrameProducer
      interface as it's no longer needed.
      Currently video scaling is only used in the plugin when Graphics3D is
      not available. In that case Graphics2D::SetScale() performs better than
      trying to scale the image in the plugin, especially given that the
      scaling code is not optimized for PNaCl.
      This refactoring also allowed to simplify threading logic in the
      rendering both on Android and in the plugin.
      BUG=256850, 486917, 509914
      Review URL: https://codereview.chromium.org/1288063004
      Cr-Commit-Position: refs/heads/master@{#344404}
  7. 17 Jul, 2015 1 commit
    • wez's avatar
      Allow shaped-desktop hosts to send shape only when it changes. · 070889be
      wez authored
      Previously hosts supplying a shaped desktop needed to attach the desktop
      shape to every frame, wasting bandwidth since the shape changes
      relatively infrequently.
      This CL updates the VideoRenderer implementations to preserve the shape
      (or lack of one) from the preceding frame if the VideoPacket does not
      include the use_desktop_shape field.
      Also simplifies FrameConsumerProxy to remove the need for ref-counting,
      updates NULL->nullptr throughout remoting/codec/, and removes
      unnecessary transparency logic from VideoDecoderVpx.
      Review URL: https://codereview.chromium.org/1236663002
      Cr-Commit-Position: refs/heads/master@{#339212}
  8. 23 Jan, 2014 1 commit
  9. 02 Oct, 2013 1 commit
  10. 25 Sep, 2013 1 commit
  11. 19 Sep, 2013 2 commits
  12. 17 Jul, 2013 1 commit
  13. 04 Jul, 2013 1 commit
  14. 20 Jul, 2012 1 commit
  15. 26 Jun, 2012 1 commit
    • rsleevi@chromium.org's avatar
      RefCounted types should not have public destructors, delegate cleanup · 512d03f7
      rsleevi@chromium.org authored
      For Delegate/Observer-type classes that specify an
      interface but do not have any particular lifetime
      requirements, make their destructors protected. This is to
      allow their interfaces to be implemented safely by
      RefCounted types. With public destructors, it's possible to
      do "scoped_ptr<Delegate> foo", and then assign a
      RefCountedDelegateImpl, which would lead to a double free.
      As none of these Delegates actually need public destructors
      (ownership of the Delegate* is not transferred during a
      function call / class constructor), mark the destructors
      protected so that it becomes a compile warning to try to
      delete them via the Delegate*.
      TEST=it compiles
      Review URL: https://chromiumcodereview.appspot.com/10383262
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@144086 0039d316-1c4b-4281-b951-d872f2087c98
  16. 24 Feb, 2012 1 commit
  17. 29 Jan, 2012 1 commit
  18. 24 Jan, 2012 2 commits
  19. 11 Nov, 2011 1 commit
  20. 10 Nov, 2011 1 commit
  21. 30 Sep, 2011 3 commits
  22. 19 Jul, 2011 1 commit
  23. 04 Oct, 2010 1 commit
    • ajwong@chromium.org's avatar
      This is a monster CL. · 8ea7a167
      ajwong@chromium.org authored
      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
  24. 27 Sep, 2010 3 commits