Getting method call metadata in dbus-glib servers

Ross Burton ross at burtonini.com
Thu May 29 09:32:07 PDT 2008


On Thu, 2008-05-29 at 11:28 -0500, Matt Hoosier wrote:
> On Thu, May 29, 2008 at 11:02 AM, Ross Burton <ross at burtonini.com> wrote:
> > If you make your methods asynchronous, then you'll be given a context
> > object which lets you get the sender's bus name.
> 
> Thanks. So if I understand the approach here: it looks like you don't
> really want the method to be asynchronous (every path through it
> either returns an explicit error or uses dbus_g_method_return()); this
> is just a hack to get at the context information?

That's right.  It's not the best, but it works.  Another annotation to
get the context for non-async methods would be nice.

Ross
-- 
Ross Burton                                 mail: ross at burtonini.com
                                          jabber: ross at burtonini.com
                                     www: http://www.burtonini.com./
 PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF





More information about the dbus mailing list