<meta http-equiv="content-type" content="text/html; charset=utf-8"><div>I'm on an embedded environment and only have glib 2.10.6, not 2.26 or newer.</div><div>I'll try to cross compile the newer glib to my platform.</div> <div><br></div><div>Just one last related question:</div><div>If I make that dbus-glib modification that I sent in the first email, I'll be able to use a GMainLoop other than the default one.</div><div>So I can create a thread an run this main loop in it.</div> <div>The default main loop must be running too? (looks like so).</div><div><br></div><div>Thanks very much.</div><div><br></div><div><div class="gmail_quote">On Fri, Mar 11, 2011 at 11:28 AM, Colin Walters <span dir="ltr"><<a href="mailto:walters@verbum.org">walters@verbum.org</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On Fri, Mar 11, 2011 at 9:15 AM, Marcus Nascimento <<a href="mailto:marcus.cps@gmail.com">marcus.cps@gmail.com</a>> wrote:<br> ><br> > Long story short: Do you recommend moving on from glib-dbus to GDbus in this<br> > case?<br> <br> </div>Yes, if you can. But it's also worth saying that in a lot of cases,<br> it's not too difficult to structure dbus-glib code such that worker<br> threads queue an idle handler to send their data back to the main<br> loop, which then sends the reply message.<br> <br> For reference this is the longstanding bug:<br> <a href="https://bugs.freedesktop.org/show_bug.cgi?id=857" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=857</a><br> </blockquote></div><br><br clear="all"><br>-- <br>--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=<br>Marcus Vinícius do Nascimento<br>Engenharia de Computação - EC03 - UNICAMP<br>--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=<br> </div>