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

frederic heem frederic.heem at
Fri Sep 8 03:24:22 PDT 2006

Alle 12:11, venerdì 8 settembre 2006, Thiago Macieira ha scritto:
> frederic heem wrote:
> >Hi,
> >On the server side with glib binding, the annotation
> >org.freedesktop.DBus.GLib.Async means the call is asynchronous. On the
> > client side however, qt bindings are used, At the moment, dbusxml2cpp
> > doesn't handle asynchrounous call. Since the asynchronous annotation is
> > not specific to any binding, it should be better to use
> > "org.freedesktop.DBus.Method.Async", just like the annotation
> > org.freedesktop.DBus.Method.NoReply.
> The two annotations are not the same.
There is not yet an annotation for asynchronous call for qt binding and I have 
no other solution that to modify dbusxml2cpp. We have to agree on an unique 
name for asynchronous call annotation. Also, the xml interface file has to be 
the same for client/server glib/qt. It doesn't make sense to use the 
annotation org.freedesktop.DBus.GLib.Async or org.freedesktop.DBus.Qt.Async 
or org.freedesktop.DBus.<PutYourFavorityBinding>.Async.  The asynchronous 
property does *not* depend on the binding type, no its name shall not contain 
the name of the binding.


--- NOTICE ---

CONFIDENTIALITY - This  email  and  any  attachments  are confidential and are
intended  for  the  addressee  only.   If  you  have  received this message by
mistake,  please  contact us immediately and then delete the message from your
system.  You  must  not copy, distribute, disclose or act upon the contents of
this email. Thank you.

PERSONAL DATA PROTECTION  (Law  by  Decree  30. 06.2003 n. 196) - Personal and
corporate  data  submitted  will  be used in a correct, transparent and lawful
manner. The data collected will be processed in paper or computerized form for
the performance of contractual  and  lawful  obligations  as  well  as for the
effective management of business relationship. Data may be disclosed, in Italy
or abroad, for the purpose above mentioned to third  parties  which  cooperate
with Telsey, agents, banks, factoring companies,  credit recovering companies,
credit  insurance  companies,  professional  and  consultants,  and   shipping
companies. In relation to the same purposes, data  may  be  processed  by  the
following  classes  of  executors  or  processors:  management; administration
department; logistics  and  purchase  department; sales department; post sales
department quality department; R&D department; IT department; legal department.
The  data  processor  is  Telsey S.p.A.  The data subject may exercise all the
rights set forth in art. 7 of Law by Decree 30. 06.2003 n. 196 as reported  in
in the following link 


More information about the dbus mailing list