Skip to content
  • 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