<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
<br>
On 10/12/10 18:41, Ian Monroe wrote:
<blockquote
cite="mid:AANLkTikUsseh9oanVpscFjG9zAVLdzmWRmoW8kXX9pfZ@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Fri, Dec 10, 2010 at 12:12, Conor
Curran <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:conor.curran@canonical.com">conor.curran@canonical.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div text="#000000" bgcolor="#ffffff"> I just did some
research on the vala dbus async api. It looks as if the good
vala people have taken care of the async behaviour.
Therefore the GetPlaylists can pretty much stay the same. <br>
</div>
</blockquote>
<div><br>
How can vala people take care of the async behavior? A d-bus
api that is sync is sync, nothing a dbus binding can change
about that. Your initial reasons for needing async are unclear
to me, perhaps this is why I'm confused.<br>
<br>
</div>
</div>
</blockquote>
<br>
It is asynchronous in relation to the application thread. Vala will
offline the dbus call to a separate thread and come back once it's
ready. This is all I basically need so that my app does not block if
something goes screwy happens with that call. That is all I was
looking for.<br>
<br>
Good weekend.<br>
Conor<br>
<br>
</body>
</html>