Hi, On Mon, Sep 14, 2009 at 6:11 PM, Johan Hedberg <johan.hedberg@xxxxxxxxx> wrote: > Thanks! The patch has now been pushed upstream. > > One thing that came to my mind is that it might be possible to simplify > the code by making the introspection interface less of a special case > within gdbus: > > Instead of hard coding this XML snippet and handling the Introspect method > call separately from the rest of the method calls for a particular object > path gdbus could use its own public interface registration system > (i.e. g_dbus_register_interface) to implicitly register the Introspectable > interface as the first interface when creating new object paths. This way > the existing interface callback mechanism would do most of the work and > there wouldn't be a need to explicitly add the extra snippet to the XML > output like your patch now does. > > Any thoughts on this? Yep, that sounds better for me too. About the qdbus tool, I remember having this issue some time ago, but it seems that any instance of QDBusInterface triggers introspect, but qdbus code add another check for Introspectable interface which seems unnecessary because it does that to call introspect again. -- Luiz Augusto von Dentz Engenheiro de Computação -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
