1. 31 Mar, 2012 1 commit
  2. 18 Oct, 2011 1 commit
  3. 07 Oct, 2011 1 commit
  4. 20 Jun, 2011 1 commit
  5. 07 Aug, 2010 1 commit
    • Matthias Clasen's avatar
      Make the closure variants of name owning and watching actually work · 402ad195
      Matthias Clasen authored
      The GClosure API is a bit funky (and badly documented), and requires
      you to set a marshaller on the closure, and the marshaller has an
      implicit 'this' argument, and the caller is reponsible for unsetting
      the values after invoking the closure.
      
      I've added some calls of the _with_closures variants to the
      gdbus-names test now.
      402ad195
  6. 19 Jul, 2010 1 commit
  7. 07 Jul, 2010 1 commit
  8. 29 Jun, 2010 1 commit
    • David Zeuthen's avatar
      Bug 623143 – Never require non-closed connections · 6d4ade4c
      David Zeuthen authored
      There's a couple of places in GDBus where it's a programming error
      (e.g. we'll assert or spew via e.g. g_warning()) to use the API on a
      closed connection.  This approach can never work since a
      GDBusConnection can be closed at any point in time outside of
      programmer control.
      
      Just change the code to return a run-time error (e.g. return
      G_IO_ERROR_CLOSED when sending messages, invoking methods) or silently
      accept the request (e.g.  exporting objects, registering for signals)
      without doing anything.
      
      Note that a GDBusConnection object is always useless after being
      closed - e.g.  there's no way to "reopen" a connection - the user will
      have to create a new object and use that instead.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=623143Signed-off-by: 's avatarDavid Zeuthen <davidz@redhat.com>
      6d4ade4c
  9. 18 Jun, 2010 1 commit
  10. 10 Jun, 2010 1 commit
  11. 24 May, 2010 1 commit
    • Allison Karlitskaya's avatar
      GDBusConnection.call(): add 'reply_type' argument · 3160bcad
      Allison Karlitskaya authored
      This allows the caller to specify the reply type that they are expecting
      for this call.  If the reply comes back with the wrong type, GDBus will
      generate an appropriate error internally.
      
        - add a GVariantType * argument to g_dbus_connection_call() and
          _call_sync().
      
        - move the internal API for computing message types from introspection
          data to be based on GVariantType instead of strings.  Update users
          of this code.
      
        - have GDBusProxy pass this calculated GVariantType into
          g_dbus_connection_call().  Remove the checks done in GDBusProxy.
      
        - Update other users of the code (test cases, gdbus-tool, GSettings
          tool, etc).  In some cases, remove redundant checks; in some other
          cases, we are fixing bugs because no checking was done where it
          should have been.
      
      Closes bug #619391.
      3160bcad
  12. 13 May, 2010 3 commits
  13. 10 May, 2010 1 commit
    • David Zeuthen's avatar
      GDBus: Use call() instead of invoke_method() · 869b4c68
      David Zeuthen authored
      Lots of people been suggesting this. We still use MethodInvocation /
      method_invocation for handling incoming method calls so use call()
      instead of invoke_method() helps to separate the client and server
      facilities. Which is a good thing(tm).
      869b4c68
  14. 09 May, 2010 1 commit
  15. 06 May, 2010 5 commits