Documentation/Maemo 5 Developer Guide/DBus/Asynchronous Glib/D-Bus

=Asynchronous GLib/D-Bus =

The example code used below can be found in the garage svn.

Asynchronicity in D-Bus clients
So far all the RPC method calls that have been implemented here have been "fast", i.e. their execution has not depended on an access to slow services or external resources. In real life, however, it is quite likely that some services cannot be provided immediately, but will have to wait for some external service to complete, before completing the method call.

The GLib wrappers provide a version of making method calls, where the call will be launched (almost) immediately, and a callback will be executed when the method call returns (either with a return value, or an error).

Using the asynchronous wrappers is important, when the program needs to update some kind of status, or be reactive to the user (via a GUI or other interface). Otherwise, the program would block waiting for the RPC method to return, and would not be able to refresh the GUI or screen when required. An alternative solution would be to use separate threads that would run the synchronous methods, but synchronization between threads would become an issue, and debugging threaded programs is much harder than single-threaded ones. Also, implementation of threads might be suboptimal in some environments. These are the reasons why the thread scenario will not be covered here.

Slow running RPC methods will be simulated here by adding a delay into the server method implementations, so that it will become clear why asynchronous RPC mechanisms are important. As signals, by their nature, are asynchronous as well, they do not add anything to this example now. In order to simplify the code listings, the signal support from the asynchronous clients will be dropped here, even though the server still contains them and will emit the.

Slow Test Server
The only change on the server side is the addition of delays into each of the RPC methods (setvalue1, setvalue2, getvalue1 and getvalue2). This delay is added to the start of each function as follows: glib-dbus-async/server.c

 '' /* How many microseconds to delay between each client operation. */ ''   #define    SERVER_DELAY_USEC   (  5   * 1000000UL ) '' /*... Listing cut for brevity ...*/ '' gboolean  value_object_setvalue1  ( ValueObject  * obj , gint valueIn ,                                                    GError  ** error )  <font color="#FF0000">{  <font color="#000000">dbg  <font color="#990000">(  <font color="#FF0000">"Called (valueIn=%d)"  <font color="#990000">, valueIn <font color="#990000">);  <font color="#000000">g_assert  <font color="#990000">( obj <font color="#990000"> != NULL <font color="#990000">);  <font color="#000000">dbg  <font color="#990000">(  <font color="#FF0000">"Delaying operation"  <font color="#990000">);  <font color="#000000">g_usleep  <font color="#990000">( SERVER_DELAY_USEC <font color="#990000">); '' <font color="#9A1900">/* Compare the current value against old one. If they're the same, '' '' <font color="#9A1900">    we don't need to do anything (except return success). */ ''    <font color="#0000FF">if   <font color="#990000">( obj <font color="#990000">-&gt; value1 <font color="#990000"> != valueIn <font color="#990000">)  <font color="#FF0000">{ </tt>

Building the server is done as before, but we'll notice the delay when we call an RPC method:

[sbox-FREMANTLE_X86: ~/glib-dbus-async] &gt; run-standalone.sh ./server &amp; server:main Connecting to the Session D-Bus. server:main Registering the well-known name (org.maemo.Platdev_ex) server:main RequestName returned 1. server:main Creating one Value object. server:value_object_class_init: Called server:value_object_class_init: Creating signals server:value_object_class_init: Binding to GLib/D-Bus server:value_object_class_init: Done server:value_object_init: Called server:main Registering it on the D-Bus. server:main Ready to serve requests (daemonizing). server: Not daemonizing (built with NO_DAEMON-build define) [sbox-FREMANTLE_X86: ~/glib-dbus-async] &gt; time run-standalone.sh dbus-send \ --type=method_call --print-reply --dest=org.maemo.Platdev_ex \ /GlobalValue org.maemo.Value.getvalue1 server:value_object_getvalue1: Called (internal value1 is 0) server:value_object_getvalue1: Delaying operation method return sender=:1.54 -&gt; dest=:1.56 int32 0 real   0m5.066s user   0m0.004s sys    0m0.056s

In the example above, the time shell built-in command was used. It will run the given command while measuring the wall clock time (a.k.a. real time), and time used while executing the code and system calls. In this case, only the real time is of any interest. The method call will delay for about 5 seconds, as it should. The delay (even if given with microsecond resolution) is always approximate, and longer than the requested amount. Exact delay will depend on many factors, most of which cannot be directly influenced.

The next experiment deals with a likely scenario, where another method call comes along while the first one is still being executed. This is best tested by just repeating the sending command twice, but running the first one on the background (so that the shell does not wait for it to complete first). The server is still running on the background from the previous test:

[sbox-FREMANTLE_X86: ~/glib-dbus-async] &gt; time run-standalone.sh dbus-send \ --type=method_call --print-reply --dest=org.maemo.Platdev_ex \ /GlobalValue org.maemo.Value.getvalue1 &amp; [2] 17010 server:value_object_getvalue1: Called (internal value1 is 0) server:value_object_getvalue1: Delaying operation [sbox-FREMANTLE_X86: ~/glib-dbus-async] &gt; time run-standalone.sh dbus-send \ --type=method_call --print-reply --dest=org.maemo.Platdev_ex \ /GlobalValue org.maemo.Value.getvalue1 method return sender=:1.54 -&gt; dest=:1.57 int32 0 real   0m5.176s user   0m0.008s sys    0m0.092s server:value_object_getvalue1: Called (internal value1 is 0) server:value_object_getvalue1: Delaying operation method return sender=:1.54 -&gt; dest=:1.58 int32 0 real   0m9.852s user   0m0.004s sys    0m0.052s

What can be seen from the above output is that the first client is delayed for about 5 seconds, while the second client (which was launched shortly after the first) is already delayed by a much longer period. This is to be expected, as the server can only process one request at a time, and will delay each request by 5 seconds.

Some server concurrency issues will be covered later, but for now, it is necessary that the clients are able to continue their "normal work" while they wait for the response from the server. Since this is just example code, "normal work" for our clients would be just waiting for the response, while blocking on incoming events (converted into callbacks). However, if the example programs were graphical, the asynchronous approach would make it possible for them to react to user input. D-Bus by itself does not support cancellation of method calls, once processing has started on the server side, so adding cancellation support would require a separate method call to the server. Since the server only handles one operation at a time, the current server cannot support method call cancellations at all.

Asynchronous Method Calls Using Stubs
When the glib-bindings-tool is run, it will already generate the necessary wrapping stubs to support launching asynchronous method calls. What is then left to do is implementing the callback functions correctly, processing the return errors and launching the method call. glib-dbus-async/client-stubs.c

<tt>  <font color="#9A1900">/* Pull in the client stubs that were generated with   <font color="#9A1900">  dbus-binding-tool */   <font color="#000080"> #include  <font color="#FF0000">"value-client-stub.h" </tt>

The client has been simplified, so that it now only operates on value1. The callback that is called from the stub code is presented next: glib-dbus-async/client-stubs.c

<tt>  <font color="#9A1900">/**   <font color="#9A1900"> * This function will be called when the async setvalue1 will either   <font color="#9A1900"> * complete, timeout or fail (our server however does not signal  '' <font color="#9A1900"> * errors, but the client D-Bus library might). When this example '' '' <font color="#9A1900"> * program is left running for a while, you will see all three cases.   <font color="#9A1900"> * ''  <font color="#9A1900"> * The prototype must match the one generated by the dbus-binding-tool  '' <font color="#9A1900"> * (org_maemo_Value_setvalue1_reply).   <font color="#9A1900"> * ''  <font color="#9A1900"> * Since there is no return value from the RPC, the only useful  '' <font color="#9A1900"> * parameter that we get is the error object, which we'll check.   <font color="#9A1900"> * If error is NULL, that means no error. Otherwise the RPC call '' '' <font color="#9A1900"> * failed and we should check what the cause was.   <font color="#9A1900"> */ ''  <font color="#0000FF">static  <font color="#009900">void   <font color="#000000">setValue1Completed   <font color="#990000">( DBusGProxy <font color="#990000"> * proxy <font color="#990000">, GError <font color="#990000"> * error <font color="#990000">,                                                    gpointer userData <font color="#990000">)  <font color="#FF0000">{  <font color="#000000">g_print  <font color="#990000">( PROGNAME <font color="#FF0000">":%s:setValue1Completed  <font color="#CC33CC">\n  <font color="#FF0000">"  <font color="#990000">,   <font color="#000000">timestamp   <font color="#990000">);  <font color="#0000FF">if  <font color="#990000">( error <font color="#990000"> != NULL <font color="#990000">)  <font color="#FF0000">{  <font color="#000000">g_printerr  <font color="#990000">( PROGNAME <font color="#FF0000">"       ERROR: %s  <font color="#CC33CC">\n  <font color="#FF0000">"  <font color="#990000">, error <font color="#990000">-&gt; message <font color="#990000">);  <font color="#9A1900">/* We need to release the error object since the stub code does  '' <font color="#9A1900">      not do it automatically. */ ''      <font color="#000000">g_error_free   <font color="#990000">( error <font color="#990000">); <font color="#FF0000">}  <font color="#0000FF">else   <font color="#FF0000">{  <font color="#000000">g_print  <font color="#990000">( PROGNAME <font color="#FF0000">"       SUCCESS  <font color="#CC33CC">\n  <font color="#FF0000">"  <font color="#990000">); <font color="#FF0000">} <font color="#FF0000">} </tt>

Since the method call does not return any data, the parameters for the callback are at minimum (those three will always be received). Handling errors must be performed within the callback, since errors could be delayed from the server, and not visible immediately at launch time. N.B. The callback will not terminate the program on errors. This is done on purpose in order to demonstrate some common asynchronous problems below. The timestamp function is a small utility function to return a pointer to a string, representing the number of seconds since the program started (useful to visualize the order of the different asynchronous events below). glib-dbus-async/client-stubs.c

<tt>  <font color="#9A1900">/**   <font color="#9A1900"> * This function will be called repeatedly from within the mainloop  '' <font color="#9A1900"> * timer launch code.   <font color="#9A1900"> * ''  <font color="#9A1900"> * It will launch asynchronous RPC method to set value1 with ever  '' <font color="#9A1900"> * increasing argument.   <font color="#9A1900"> */ ''  <font color="#0000FF">static  gboolean  <font color="#000000">timerCallback  <font color="#990000">( DBusGProxy <font color="#990000"> * remoteobj <font color="#990000">)  <font color="#FF0000">{ '' <font color="#9A1900">/* Local value that we'll start updating to the remote object. */ ''    <font color="#0000FF">static  gint localValue1 <font color="#990000"> =  <font color="#990000">-  <font color="#993399">80  <font color="#990000"> ; '' <font color="#9A1900">/* Start the RPC.   <font color="#9A1900">     This is done by calling the stub function that will take the new '' '' <font color="#9A1900">    value and the callback function to call on reply getting back.   <font color="#9A1900">     The stub returns a DBusGProxyCall object, but we don't need it '' '' <font color="#9A1900">    so we'll ignore the return value. The return value could be used ''  <font color="#9A1900">    to cancel a pending request (from client side) with  '' <font color="#9A1900">    dbus_g_proxy_cancel_call. We could also pass a pointer to '' '' <font color="#9A1900">    user-data (last parameter), but we don't need one in this example.   <font color="#9A1900">     It would normally be used to "carry around" the application state.   <font color="#9A1900">     */ ''  <font color="#000000">g_print  <font color="#990000">( PROGNAME <font color="#FF0000">":%s:timerCallback launching setvalue1  <font color="#CC33CC">\n  <font color="#FF0000">"  <font color="#990000">,             <font color="#000000">timestamp   <font color="#990000">);  <font color="#000000">org_maemo_Value_setvalue1_async  <font color="#990000">( remoteobj <font color="#990000">, localValue1 <font color="#990000">,                                    setValue1Completed <font color="#990000">, NULL <font color="#990000">);  <font color="#000000">g_print  <font color="#990000">( PROGNAME <font color="#FF0000">":%s:timerCallback setvalue1 launched  <font color="#CC33CC">\n  <font color="#FF0000">"  <font color="#990000">,             <font color="#000000">timestamp   <font color="#990000">); '' <font color="#9A1900">/* Step the local value forward. */ ''   localValue1 <font color="#990000">+=  <font color="#993399">10  <font color="#990000"> ; '' <font color="#9A1900">/* Repeat timer later. */ ''    <font color="#0000FF">return  TRUE <font color="#990000"> ; <font color="#FF0000">} </tt>

Using the stub code is rather simple. For each generated synchronous version of a method wrapper, there will also be a _async version of the call. The main difference with the parameters is the removal of the GError pointer (since errors will be handled in the callback), and the addition of the callback function to use when the method completes, times out or encounters an error.

The main function remains the same from the previous client examples (a once-per-second timer will be created and run from the mainloop, until the program is terminated).

Problems with Asynchronicity
When the simple test program is built and run, it can be seen that everything starts off quite well. But at some point, problems will start to appear:

What happens above is rather subtle. The timer callback in the client launches once per second and performs the RPC method launch. The server, however, still has the 5 second delay for each method call in it. It can be seen that the successive launches go on without any responses for a while. The first response comes back at about 6 seconds from the starting of the client. At this point, the server already has four other outstanding method calls that it has not handled. Slowly the method calls are accumulating at the server end, and it does not deal with them quickly enough to satisfy the client.

After about 30 seconds, it can be seen how the setValue1Completed callback is invoked, but the method call fails. This has managed to trigger the method call timeout mechanism. After this point, all the method calls that have accumulated into the server (into a message queue) will fail in the client, since they all will now return late, even if the server actually does handle them.

Once the client is terminated, it can be seen that the server is still happily continuing serving the requests, oblivious to the fact that there is no client to process the responses.

The above test demonstrates quite brutally that the services need to be designed properly, so that there is a clearly defined protocol what to do in case a method call is delayed. It is also advisable to design a notification protocol to tell clients that something has completed, instead of forcing them to time out. Using D-Bus signals is one way, but it is necessary to take care not to generate signals, when tere is nothing listening to them. This can be done by only sending signals when an long operation finishes (assuming this has been documented as part of the service description).

One partial fix would be for the client to track and make sure that only one method call to one service is outstanding at any given time. So, instead of just blindly launching the RPC methods, it should defer from launching, if it has not yet received a response from the server (and the call has not timed out).

However, this fix is not complete, since the same problem will manifest itself once there are multiple clients running in parallel and requesting the same methods. The proper fix is to make the server capable of serving multiple requests in parallel. Some hints on how to do this are presented later on.

Asynchronous Method Calls Using GLib Wrappers
Sometimes the interface XML will be missing, so the dbus-bindings-tool cannot be run to generate the stub code. The GLib wrappers are generic enough to enable building own method calls, when necessary.

It is often easiest to start with some known generated stub code to see, which parts can possibly be reused with some modifications. This is what is shown in the last step of this example, in order to make a version of the asynchronous client that will work without the stub generator.

The first step is to take a peek at the stub-generated code for the setvalue1 call (when used asynchronously): glib-dbus-async/value-client-stub.h

<tt>  <font color="#0000FF">typedef  <font color="#009900">void  <font color="#990000">(* org_maemo_Value_setvalue1_reply <font color="#990000">)  <font color="#990000">( DBusGProxy <font color="#990000"> * proxy <font color="#990000">,                                                   GError <font color="#990000"> * error <font color="#990000">,                                                   gpointer userdata <font color="#990000">);  <font color="#0000FF">static  <font color="#009900">void  <font color="#000000">org_maemo_Value_setvalue1_async_callback  <font color="#990000">( DBusGProxy <font color="#990000"> * proxy <font color="#990000">,                                            DBusGProxyCall <font color="#990000"> * call <font color="#990000">,                                            <font color="#009900">void  <font color="#990000"> * user_data <font color="#990000">) <font color="#FF0000">{ DBusGAsyncData <font color="#990000"> * data <font color="#990000"> = user_data <font color="#990000"> ; GError <font color="#990000"> * error <font color="#990000"> = NULL <font color="#990000"> ;  <font color="#000000">dbus_g_proxy_end_call  <font color="#990000">( proxy <font color="#990000">, call <font color="#990000">,  <font color="#990000">&amp; error <font color="#990000">, G_TYPE_INVALID <font color="#990000">); <font color="#990000">(*( org_maemo_Value_setvalue1_reply <font color="#990000">) data <font color="#990000">-&gt; cb <font color="#990000">) <font color="#990000">( proxy <font color="#990000">, error <font color="#990000">,                                                  data <font color="#990000">-&gt; userdata <font color="#990000">);  <font color="#0000FF">return  <font color="#990000"> ; <font color="#FF0000">}  <font color="#0000FF">static   <font color="#000080"> #ifdef  G_HAVE_INLINE inline  <font color="#000080"> #endif  DBusGProxyCall <font color="#990000"> *  <font color="#000000">org_maemo_Value_setvalue1_async  <font color="#990000">( DBusGProxy <font color="#990000"> * proxy <font color="#990000">,                                    <font color="#0000FF">const  gint IN_new_value <font color="#990000">,                               org_maemo_Value_setvalue1_reply callback <font color="#990000">,                                   gpointer userdata <font color="#990000">) <font color="#FF0000">{ DBusGAsyncData <font color="#990000"> * stuff <font color="#990000"> ; stuff <font color="#990000"> =  <font color="#000000">g_new   <font color="#990000">( DBusGAsyncData <font color="#990000">,  <font color="#993399">1  <font color="#990000">); stuff <font color="#990000">-&gt; cb <font color="#990000"> =  <font color="#000000">G_CALLBACK   <font color="#990000">( callback <font color="#990000">); stuff <font color="#990000">-&gt; userdata <font color="#990000"> = userdata <font color="#990000"> ;  <font color="#0000FF">return   <font color="#000000">dbus_g_proxy_begin_call   <font color="#990000">(      proxy <font color="#990000">,  <font color="#FF0000">"setvalue1"  <font color="#990000">, org_maemo_Value_setvalue1_async_callback <font color="#990000">,      stuff <font color="#990000">, g_free <font color="#990000">, G_TYPE_INT <font color="#990000">, IN_new_value <font color="#990000">, G_TYPE_INVALID <font color="#990000">); <font color="#FF0000">} </tt>

What is notable in the code snippet above is that the _async method will create a temporary small structure that will hold the pointer to the callback function, and a copy of the userdata pointer. This small structure will then be passed to dbus_g_proxy_begin_call, along with the address of the generated callback wrapper function (org_maemo_Value_setvalue1_async_callback). The GLib async launcher will also take a function pointer to a function to use when the supplied "user-data" (in this case, the small structure) will need to be disposed of after the call. Since it uses g_new to allocate the small structure, it passes g_free as the freeing function. Next comes the argument specification for the method call, which obeys the same rules as the LibOSSO ones before.

On RPC completion, the generated callback will be invoked, and it will get the real callback function pointer and the userdata as its "user-data" parameter. It will first collect the exit code for the call with dbus_g_proxy_end_call, unpack the data and invoke the real callback. After returning, the GLib wrappers (which called the generated callback) will call g_free to release the small structure, and the whole RPC launch will end.

The next step is to re-implement pretty much the same logic, but also dispose of the small structure, since the callback will be implemented directly, not as a wrapper-callback (it also omits the need for one memory allocation and one free).

The first step for that is to implement the RPC asynchronous launch code: glib-dbus-async/client-glib.c

<tt>  <font color="#9A1900">/**   <font color="#9A1900"> * This function will be called repeatedly from within the mainloop  '' <font color="#9A1900"> * timer launch code.   <font color="#9A1900"> * ''  <font color="#9A1900"> * It will launch asynchronous RPC method to set value1 with ever  '' <font color="#9A1900"> * increasing argument.   <font color="#9A1900"> */ ''  <font color="#0000FF">static  gboolean  <font color="#000000">timerCallback  <font color="#990000">( DBusGProxy <font color="#990000"> * remoteobj <font color="#990000">)  <font color="#FF0000">{ '' <font color="#9A1900">/* Local value that we'll start updating to the remote object. */ ''    <font color="#0000FF">static  gint localValue1 <font color="#990000"> =  <font color="#990000">-  <font color="#993399">80  <font color="#990000"> ; '' <font color="#9A1900">/* Start the first RPC.   <font color="#9A1900">     The call using GLib/D-Bus is only slightly more complex than the '' '' <font color="#9A1900">    stubs. The overall operation is the same. */ ''    <font color="#000000">g_print   <font color="#990000">( PROGNAME <font color="#FF0000">":timerCallback launching setvalue1  <font color="#CC33CC">\n  <font color="#FF0000">"  <font color="#990000">);  <font color="#000000">dbus_g_proxy_begin_call  <font color="#990000">( remoteobj <font color="#990000">,                             <font color="#9A1900">/* Method name. */                             <font color="#FF0000">"setvalue1"  <font color="#990000">,                             <font color="#9A1900">/* Callback to call on "completion". */                             setValue1Completed <font color="#990000">,                             <font color="#9A1900">/* User-data to pass to callback. */                             NULL <font color="#990000">,                             <font color="#9A1900">/* Function to call to free userData after    <font color="#9A1900">                             callback returns. */                             NULL <font color="#990000">,                             <font color="#9A1900">/* First argument GType. */  G_TYPE_INT <font color="#990000">,  <font color="#9A1900">/* First argument value (passed by value) */  localValue1 <font color="#990000">, '' <font color="#9A1900">/* Terminate argument list. */                            G_TYPE_INVALID <font color="#990000">);     <font color="#000000">g_print   <font color="#990000">( PROGNAME <font color="#FF0000">":timerCallback setvalue1 launched  <font color="#CC33CC">\n  <font color="#FF0000">"  <font color="#990000">);     <font color="#9A1900">/* Step the local value forward. */     localValue1 <font color="#990000">+=  <font color="#993399">10  <font color="#990000"> ;     <font color="#9A1900">/* Repeat timer later. */ ''     <font color="#0000FF">return  TRUE <font color="#990000"> ;  <font color="#FF0000">} </tt>

And the callback that will be invoked on method call completion, timeouts or errors: glib-dbus-async/client-glib.c

<tt>  <font color="#9A1900">/**   <font color="#9A1900"> * This function will be called when the async setvalue1 will either  '' <font color="#9A1900"> * complete, timeout or fail (same as before). The main difference in ''  <font color="#9A1900"> * using GLib/D-Bus wrappers is that we need to "collect" the return  '' <font color="#9A1900"> * value (or error). This is done with the _end_call function.   <font color="#9A1900"> * ''  <font color="#9A1900"> * Note that all callbacks that are to be registered for RPC async   <font color="#9A1900"> * notifications using dbus_g_proxy_begin_call must follow the  '' <font color="#9A1900"> * following prototype: DBusGProxyCallNotify.   <font color="#9A1900"> */ ''  <font color="#0000FF">static  <font color="#009900">void   <font color="#000000">setValue1Completed   <font color="#990000">( DBusGProxy <font color="#990000"> * proxy <font color="#990000">,                                 DBusGProxyCall <font color="#990000"> * call <font color="#990000">,                                 gpointer userData <font color="#990000">)  <font color="#FF0000">{ '' <font color="#9A1900">/* This will hold the GError object (if any). */ ''   GError <font color="#990000"> * error <font color="#990000"> = NULL <font color="#990000"> ;  <font color="#000000">g_print  <font color="#990000">( PROGNAME <font color="#FF0000">":setValue1Completed  <font color="#CC33CC">\n  <font color="#FF0000">"  <font color="#990000">); '' <font color="#9A1900">/* We next need to collect the results from the RPC call.   <font color="#9A1900">     The function returns FALSE on errors (which we check), although '' '' <font color="#9A1900">    we could also check whether error-ptr is still NULL. */ ''    <font color="#0000FF">if   <font color="#990000">(!   <font color="#000000">dbus_g_proxy_end_call   <font color="#990000">( proxy <font color="#990000">, '' <font color="#9A1900">/* The call that we're collecting. */ ''                              call <font color="#990000">, '' <font color="#9A1900">/* Where to store the error (if any). */ ''                              <font color="#990000">&amp; error <font color="#990000">,  <font color="#9A1900">/* Next we list the GType codes for all  '' <font color="#9A1900">                               the arguments we expect back. In our ''  <font color="#9A1900">                               case there are none, so set to  '' <font color="#9A1900">                               invalid. */ ''                              G_TYPE_INVALID <font color="#990000">))  <font color="#FF0000">{ '' <font color="#9A1900">/* Some error occurred while collecting the result. */ ''      <font color="#000000">g_printerr   <font color="#990000">( PROGNAME <font color="#FF0000">" ERROR: %s  <font color="#CC33CC">\n  <font color="#FF0000">"  <font color="#990000">, error <font color="#990000">-&gt; message <font color="#990000">);  <font color="#000000">g_error_free  <font color="#990000">( error <font color="#990000">); <font color="#FF0000">}  <font color="#0000FF">else   <font color="#FF0000">{  <font color="#000000">g_print  <font color="#990000">( PROGNAME <font color="#FF0000">" SUCCESS  <font color="#CC33CC">\n  <font color="#FF0000">"  <font color="#990000">); <font color="#FF0000">} <font color="#FF0000">} </tt>

The generated stub code is no longer needed, so the dependency rules for the stubless GLib version will also be somewhat different: glib-dbus-async/Makefile

<tt>client-glib <font color="#990000"> : client-glib <font color="#990000">. o        <font color="#009900">$(CC)  <font color="#009900">$^ -o <font color="#009900">$@  <font color="#009900">$(LDFLAGS) '' <font color="#9A1900"> # Note that the GLib client doesn't need the stub code. '' client-glib <font color="#990000">. o <font color="#990000"> : client-glib <font color="#990000">. c common-defs <font color="#990000">. h        <font color="#009900">$(CC)  <font color="#009900">$(CFLAGS) -DPROGNAME <font color="#990000"> = \" <font color="#009900">$( basename <font color="#009900">$@  <font color="#990000">) \" -c <font color="#009900">$&lt; -o <font color="#009900">$@ </tt>

Since the example program logic has not changed from the previous version, testing client-glib is not presented here (it can of course be tested if so desired, since the source code contains the fully working program). This version of the client will also launch the method calls without waiting for previous method calls to complete.