1. 14 Mar, 2018 2 commits
  2. 29 May, 2017 1 commit
  3. 28 Apr, 2017 1 commit
    • Philip Withnall's avatar
      docs: Fix (nullable) (optional) annotations · b63469d7
      Philip Withnall authored
      There are a few places where commit 18a33f72 replaced valid (nullable)
      (optional) annotations with just (optional). That has a different
      meaning.
      
      (nullable) (optional) can only be applied to gpointer* parameters, and
      means that both the gpointer* and returned gpointer can be NULL. i.e.
      The caller can pass in NULL to ignore the return value; and the returned
      value can be NULL.
      
      (optional) can be applied to anything* parameters, and means that the
      anything* can be NULL. i.e. The caller can pass in NULL to ignore the
      return value. The return value cannot be NULL.
      Signed-off-by: Philip Withnall's avatarPhilip Withnall <withnall@endlessm.com>
      b63469d7
  4. 22 Nov, 2016 1 commit
  5. 29 Jun, 2016 1 commit
  6. 01 May, 2015 1 commit
  7. 04 Apr, 2015 1 commit
  8. 23 Jun, 2014 1 commit
  9. 31 Jan, 2014 1 commit
  10. 08 Jan, 2014 1 commit
  11. 24 Jun, 2013 2 commits
  12. 03 Dec, 2012 1 commit
  13. 10 Oct, 2012 1 commit
  14. 20 Apr, 2011 1 commit
  15. 01 Feb, 2011 1 commit
  16. 29 Dec, 2010 1 commit
  17. 03 Nov, 2010 2 commits
  18. 24 Sep, 2010 1 commit
  19. 29 Jul, 2010 1 commit
    • Eduardo Lima Mitev's avatar
      GIO: Add G-I annotations for several methods · 8673f0b0
      Eduardo Lima Mitev authored
      Specifically:
       - g_io_stream_get_input/output_stream()
       - g_socket_client_get_local_address()
       - g_socket_connection_get_socket()
       - g_socket_listener_add_address()
       - g_socket_listener_accept_socket()
       - g_socket_listener_accept()
       - g_io_extension_point_get_extensions()
      8673f0b0
  20. 11 Jul, 2010 1 commit
  21. 07 Jul, 2010 1 commit
  22. 19 Nov, 2009 2 commits
  23. 01 Jul, 2009 1 commit
  24. 30 Jun, 2009 1 commit
    • Dan Winship's avatar
      Add GCancellables to GSocket ops · 53beca95
      Dan Winship authored
      Currently, to implement cancellability correctly, all synchronous
      calls to GSocket must be preceded by a g_socket_condition_wait() call,
      (even though GSocket does this internally as well) and all
      asynchronous calls must do occasional manual
      g_cancellable_is_cancelled() checks. Since it's trivial to do these
      checks inside GSocket instead, and we don't particularly want to
      encourage people to use the APIs non-cancellably, move the
      cancellation support into GSocket and simplify the existing callers.
      
      http://bugzilla.gnome.org/show_bug.cgi?id=586797
      53beca95
  25. 18 Jun, 2009 2 commits
  26. 15 Jun, 2009 3 commits
  27. 12 Jun, 2009 2 commits
    • Allison Karlitskaya's avatar
      Bug 585575 – g_socket_listener_add_inet_port() · cb1a6092
      Allison Karlitskaya authored
      Change the logic in g_socket_listener_add_inet_port() as per the
      reasoning in the bug report.
      
        - If the OS supports neither IPv6 or IPv4, fail.
        - If the OS supports only IPv6, do that.
        - If the OS supports only IPv4, do that.
        - If the OS supports IPv6 and IPv6 "speaks" IPv4 then bind it
          and be done.
        - If the OS supports IPv6 and IPv6 doesn't "speak" IPv4 then
          create an additional socket for IPv4.
        - If binding any socket fails then fail the entire call.
      
      Also, remove the ability to call this function with port == 0.  This
      is a useless thing to do anyway since you have no way to know what
      port number was actually allocated.  We should have a separate
      function to deal with this.
      cb1a6092
    • Benjamin Otte's avatar
  28. 27 May, 2009 1 commit
  29. 20 May, 2009 1 commit
    • Alexander Larsson's avatar
      Remove protocol names, instead use an enum with common protocols · 5cd86fbd
      Alexander Larsson authored
      The whole protocol name thing is pretty weird. The getprotobyname functions
      seem to only specify one mapping for name <-> ids, so all families/types
      must use the same values. Plus the values used for the protocols are
      standardized by IANA, so are always the same.
      
      So, we drop using names for protocols, intead introducing an enum with
      a few commonly availible and used protocols.
      5cd86fbd
  30. 19 May, 2009 1 commit
  31. 18 May, 2009 1 commit
  32. 15 May, 2009 1 commit