1. 27 Dec, 2018 1 commit
  2. 14 Dec, 2018 1 commit
  3. 12 Jun, 2017 1 commit
  4. 19 Aug, 2015 1 commit
  5. 08 May, 2015 1 commit
    • Philip Withnall's avatar
      build: Auto-generate win32 .def file from libnice.sym · d3a7b315
      Philip Withnall authored
      We’ve neglected to manually update this file once too often — it’s been
      out of date for important new symbols (for example,
      nice_agent_get_io_stream()) since at least 0.1.11.
      Since the format is a simple extension of libnice.sym, we might as well
      automatically generate it at dist time.
  6. 09 Oct, 2014 1 commit
  7. 21 Aug, 2014 1 commit
  8. 07 Jul, 2014 2 commits
    • Philip Withnall's avatar
    • Philip Withnall's avatar
      build: Add GObject introspection support · 0388646b
      Philip Withnall authored
      This bumps our autoconf requirement to 2.62 (from 2.59c) and disables
      automake portability warnings.
      It does not introduce a hard dependency on gobject-introspection; but if
      available, it requires version 1.30.0. Support can be enabled with
      --enable-introspection, and is required to make distcheck.
      The generated introspection file has not been checked thoroughly, and
      may expose internal symbols. A lot of new annotations are needed to make
      many of the symbols usable.
  9. 17 May, 2014 3 commits
    • Olivier Crête's avatar
    • Youness Alaoui's avatar
      Add support for ICE-TCP · a6954838
      Youness Alaoui authored
      This is a massive commit that can't be split. We add ice-tcp support
      into the agent by creating local host tcp-active/tcp-passive candidates.
      We also need to find the local and remote candidates whenever we discover
      a peer-reflexive because their data is important to setup the peer-reflexive
      so a few changes were added to look for the local or remote candidate.
      For TCP-ACTIVE remote peer-reflexive candidates, we can't add conncheck
      pairs normally because TCP-PASSIVE (local) do not generate candidate pairs,
      and we also can't have a connection from any local host, so we can only create
      a single candidatepair with the local/remote that are connected.
      The pair->socket of a candidate check pair will hold the connected tcp socket
      (through connect for ACT or accept for PASS) and we will either have a
      remote or a local peer-reflexive which will create a new candidate pair,
      we cannot trigger checks on the initial candidate pair, we must only do it
      on the new check pairs. but in the case of a tcp-passive, we don't get a new
      local peer-reflexive candidate, so there is no new candidate with a new NiceSocket, so
      when we get a triggered check, we need to match it to the candidate check pair
      or when we select a pair, it will still use the original TCP-PASS socket.
      We must store the new connected tcp socket in the peer reflexive candidates
      since they represent that unique peer-reflx candidate's connection
    • Youness Alaoui's avatar
  10. 17 Apr, 2014 1 commit
  11. 31 Mar, 2014 1 commit
  12. 25 Feb, 2014 2 commits
  13. 31 Jan, 2014 2 commits
  14. 02 Jan, 2014 2 commits
  15. 27 Dec, 2013 1 commit
  16. 18 Dec, 2013 1 commit
  17. 01 May, 2012 1 commit
  18. 06 Mar, 2012 1 commit
  19. 13 Oct, 2011 1 commit
  20. 05 Mar, 2009 1 commit
  21. 16 Feb, 2009 1 commit
  22. 30 Oct, 2008 2 commits
  23. 02 May, 2008 1 commit
  24. 30 Apr, 2008 1 commit
  25. 26 Apr, 2008 1 commit