org.freedesktop.DBus.GLib.Async GLib specific ?

Havoc Pennington hp at
Fri Sep 8 08:00:47 PDT 2006

Thiago Macieira wrote:
> Havoc Pennington wrote:
>> The annotation just has to do with how _one app_ wants to call the
>> method in a particular context.
> Which is also my point here, for avoiding an annotation. It would mean 
> that any application should call it asynchronously (the XML file is 
> supposed to be shared).

cf. the earlier thread about installing the xml files... the original 
idea I had long ago was that apps could merge their own annotations into 
a generic XML file.

The glib bindings are enough of a mess that I think right now you 
basically have to edit the "shared" xml file to get what you want 
generated though, I don't think anyone added the 
merge/overlay-annotations feature.

I was also going to use the XML files to generate the server side, the 
plan I had was something like:

  - scan C code, generating an XML file possibly including annotations
    like "C function is foo_bar_baz()"
  - generate "typelib" (meta-object in Qt terms I believe) from the XML
  - write out the typelib as a C file to include
  - also generate a "clean" XML file (minus server-specific annotations)
    to be installed, if we support installing the files

But the "scan C code" thing was never implemented, so people just write 
an XML file that includes the "C function is" annotations, and if they 
were to scrub the installed file they'd have to do it manually.

The name of the C function invoked to implement the object on the server 
side is pretty much totally uninteresting outside of the server process, 
of course.


More information about the dbus mailing list