1. 01 Jun, 2016 1 commit
    • sergeyu's avatar
      Use only DIPs size in ClientResolution. · 54624e1a
      sergeyu authored
      ClientResolution message contains DIPs and device size fields. DIPs
      size was marked as legacy, but it was actually used by the host. It's
      best to use DIPs for consistency with other messages, particularly
      VideoTrackLayout. marked device-pixel size as deprecated and the host
      now works when width/height fields are not specified.
      
      Review-Url: https://codereview.chromium.org/2021773002
      Cr-Commit-Position: refs/heads/master@{#397102}
      54624e1a
  2. 06 Apr, 2016 1 commit
  3. 01 Apr, 2016 1 commit
    • sergeyu's avatar
      Add VideoLayout message. · 00a67b14
      sergeyu authored
      Added new VideoLayout message that's sent from host to client when
      using WebRTC protocol. The message is used to notify the client about
      screen configuration. Currently both host and client support only a
      single video stream, but in the future the same VideoLayout message
      can be used to specify layout of multiple video streams.
      When using ICE protocol the message is not sent and instead it's
      generated on the client side by ClientVideoDispatcher.
      
      Review URL: https://codereview.chromium.org/1844143002
      
      Cr-Commit-Position: refs/heads/master@{#384440}
      00a67b14
  4. 03 Feb, 2016 1 commit
    • sergeyu's avatar
      Add MessagePipe interface. Use it in ChannelDispatcherBase. · f1005f6e
      sergeyu authored
      In WebRTC data streams are message-based, so the message framing
      mechanism use for the old protocol doesn't make sense for the
      WebRTC-based protocol. The new MessagePipe represents an abstract
      messaging channel. StreamMessagePipeAdapter implements framing for the
      old protocol. A different MessagePipe is going to be used for
      WebRTC-based protocol.
      
      BUG=547158
      
      Review URL: https://codereview.chromium.org/1649063003
      
      Cr-Commit-Position: refs/heads/master@{#373340}
      f1005f6e
  5. 30 Jan, 2016 2 commits
    • sergeyu's avatar
      Simplify message parsing. · d8af2cac
      sergeyu authored
      Previously ProtobufMessageParser was used to parse incoming messages.
      Removed it and replaced with ParseMessage() function. This allows to
      simplify MessageReader and makes it possible to remove MessageReader
      dependency in ChannelDispatcherBase, which will be done later.
      
      Review URL: https://codereview.chromium.org/1654513003
      
      Cr-Commit-Position: refs/heads/master@{#372526}
      d8af2cac
    • sergeyu's avatar
      Remove done notifications from incoming message handlers. · e61b68d9
      sergeyu authored
      Previously MessageReader and ProtobufMessageParse were passing done
      callbacks to the messages handlers. These callbacks were necessary to
      pace the reader, particularly when video renderer is slow and cannot
      keep up with the rate of the incoming messages. It's no longer
      necessary because we have explicit ACK messages for video packets.
      
      Review URL: https://codereview.chromium.org/1655433002
      
      Cr-Commit-Position: refs/heads/master@{#372509}
      e61b68d9
  6. 17 Jun, 2015 1 commit
  7. 10 Jan, 2015 1 commit
    • sergeyu's avatar
      Cleanup channel dispatchers · 203832d4
      sergeyu authored
      Now ChannelDispatcherBase handles initialization of reader and writer,
      which makes all dispatcher classes simpler. ChannelDispatcherBase now
      can handle writer errors. Also renamed
      ProtobufMessageReader -> ProtobufMessageParser.
      
      Review URL: https://codereview.chromium.org/841773005
      
      Cr-Commit-Position: refs/heads/master@{#310993}
      203832d4
  8. 09 Jan, 2015 1 commit
  9. 10 Apr, 2014 1 commit
  10. 30 Aug, 2013 1 commit
  11. 13 Aug, 2013 1 commit
  12. 10 Jun, 2013 1 commit
  13. 10 May, 2013 1 commit
  14. 19 Apr, 2013 1 commit
    • alexeypa@chromium.org's avatar
      Set the initial resolution of an RDP session to the client screen resolution if it is available. · a5d181f5
      alexeypa@chromium.org authored
      Changes in this CL:
       - The version of the control channel is increased to 3. This allows the host and client to tell if the peer supports capabilities negotiation or not.
       - The client and host negotiate supported capabilities by sending each other a list of the supported capabilities. Capabilities supported by both client and host are assumed to be enabled.
       - The client plugin and webapp negotiate the list of capabilities supported by the client. The webapp has the final word.
       - The DesktopEnvironment interface was extended to provide the list of all supported capabilities and receive the results of negotiation with the client.
       - Added the 'sendInitialResolution' capability. When it is enabled the client sends its screen resolution to the host once the connection has been established.
       - DesktopSessionProxy now waits for the client screen resolution when the 'sendInitialResolution' capability is enabled.
      
      BUG=230893
      
      Review URL: https://chromiumcodereview.appspot.com/13932020
      
      git-svn-id: svn://svn.chromium.org/chrome/trunk/src@195192 0039d316-1c4b-4281-b951-d872f2087c98
      a5d181f5
  15. 13 Feb, 2013 1 commit
  16. 18 Oct, 2012 1 commit
  17. 02 Jun, 2012 1 commit
  18. 24 May, 2012 1 commit
  19. 03 May, 2012 1 commit
  20. 27 Apr, 2012 1 commit
  21. 31 Mar, 2012 1 commit
  22. 28 Mar, 2012 1 commit
  23. 16 Mar, 2012 1 commit
  24. 21 Feb, 2012 1 commit
  25. 09 Feb, 2012 1 commit
  26. 08 Feb, 2012 1 commit
  27. 22 Nov, 2011 1 commit
  28. 18 Nov, 2011 1 commit