1. 01 Feb, 2018 1 commit
  2. 31 Jan, 2018 1 commit
  3. 30 Jan, 2018 1 commit
  4. 26 Jan, 2018 9 commits
  5. 25 Jan, 2018 1 commit
  6. 16 Jan, 2018 1 commit
  7. 06 Dec, 2017 1 commit
  8. 23 Nov, 2017 2 commits
  9. 21 Nov, 2017 1 commit
  10. 20 Nov, 2017 2 commits
  11. 16 Nov, 2017 4 commits
  12. 15 Nov, 2017 1 commit
  13. 14 Nov, 2017 5 commits
  14. 25 Sep, 2017 3 commits
  15. 29 Aug, 2017 6 commits
  16. 04 Jul, 2017 1 commit
    • Emanuele Aina's avatar
      IDC: Rework draft data connections API · 46677dce
      Emanuele Aina authored
      The draft data connection API relied on some magic done by the
      adapter/gateway services to convert a D-Bus call to a different one on
      the other side.
      
      This would have made the system a bit confusing and definitely harder
      to test.
      
      The updated data connections API relies instead on methods to be called
      on the adapter/gateway services that specify the bus names of
      the destination and sender SDK services.
      
      It also provides some details about what can be the actual message
      travelling across domains and how a nonce must be used to authenticate
      the new data connection.
      
      As Justin initially suggested it also no longer uses channel ids that
      must be explicitly released: at the end of the setup procedure each
      service will simply have the file descriptor of the socket, and can
      simply call close() to terminate the connection.
      
      In a similar way, the API no longer uses explict clock ids but simply
      returns the parameter string as used in RTCP.
      Signed-off-by: Emanuele Aina's avatarEmanuele Aina <emanuele.aina@collabora.com>
      Reviewed-by: default avatarJustin Kim <justin.kim@collabora.com>
      Differential Revision: https://phabricator.apertis.org/D7123
      46677dce