On Thu, May 29, 2008 at 12:32 PM, Ross Burton <<a href="mailto:ross@burtonini.com">ross@burtonini.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div class="Ih2E3d">On Thu, 2008-05-29 at 11:28 -0500, Matt Hoosier wrote:<br> > On Thu, May 29, 2008 at 11:02 AM, Ross Burton <<a href="mailto:ross@burtonini.com">ross@burtonini.com</a>> wrote:<br> > > If you make your methods asynchronous, then you'll be given a context<br> > > object which lets you get the sender's bus name.<br> ><br> > Thanks. So if I understand the approach here: it looks like you don't<br> > really want the method to be asynchronous (every path through it<br> > either returns an explicit error or uses dbus_g_method_return()); this<br> > is just a hack to get at the context information?<br> <br> </div>That's right.  It's not the best, but it works.  Another annotation to<br> get the context for non-async methods would be nice.</blockquote><div><br>A possible fix in dbus-glib is to use an internal thread-local context, exposed as a global function like<br>dbus_g_get_context() or the like.<br> </div></div><br>But yeah, it is issues like this I think that show what we really want is a nicer direct interface to DBus, not to export GObjects.<br><br>