_DBUS_APPLICATION_ID, _DBUS_UNIQUE_NAME, and _DBUS_OBJECT_PATH

[Federico Mena Quintero]

On Fri, 2011-12-16 at 01:36 +0100, Thiago Macieira wrote:

> What are other applications going to do with the object path of the window 
> object? We need a standard interface there so standard actions are possible. 
> Is there any standard you're thinking of?
> 
> For example, this KMail composer window I'm writing the email in has the 
> following interfaces:
> 
> org.kde.kmail.mailcomposer
> org.kde.kontact.KMail.Composer
> org.kde.kontact.KXmlGuiWindow
> org.kde.kontact.KMainWindow
> com.trolltech.Qt.QMainWindow
> com.trolltech.Qt.QWidget
> org.kde.KMainWindow

I'm late into the conversation, but this is very interesting stuff.

In the past I've asked, "how can we have a toplevel window export a DBus
object that can have several interfaces?".  We wanted that to do things
like asking a window, "what are the URLs of documents you are showing?".

So, can I just peek at _DBUS_UNIQUE_NAME and _DBUS_OBJECT_PATH, and see
if that object has a certain interface?

  Federico