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

frederic heem frederic.heem at
Fri Sep 8 08:35:42 PDT 2006

Regarding sharing the xml interface file, for the same method, it's valid to 
have a non-blocking method for the client, and a blocking method for the 
server, so at the moment, there is no way share this file because of this 
issue, 2 files are need, one for client and one for the server.
Worst, because of specific ways to set the asynchronous property for a method 
(org.freedesktop.DBus.GLib.Async), we will end up having one xml file for 
each binding: myInterfaceClientGlib.xml,myInterfaceServerGlib.xml, 
myInterfaceClientQt.xml,myInterfaceServerQt.xml ....
Duplicating files must be avoided for the sake of maintenance.
Let's add 2 optional attributes for the method element: blockingClient and 
blockingServer, default value shall be set to false for backward 
<method name="start" blockingClient="false" blockingServer="true">
With these 2 attributes, only one xml interface file is needed, it can used 
either for the client or the server, and with whatever language binding.
What do you think of this idea ?

Alle 15:57, venerdì 8 settembre 2006, Thiago Macieira ha scritto:
> 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).


--- 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