<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Implement pa_mainloop_api around pa_rtpoll"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73429#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Implement pa_mainloop_api around pa_rtpoll"
href="https://bugs.freedesktop.org/show_bug.cgi?id=73429">bug 73429</a>
from <span class="vcard"><a class="email" href="mailto:tanuk@iki.fi" title="Tanu Kaskinen <tanuk@iki.fi>"> <span class="fn">Tanu Kaskinen</span></a>
</span></b>
<pre>(In reply to Tanu Kaskinen from <a href="show_bug.cgi?id=73429#c0">comment #0</a>)
<span class="quote">> I think the interaction with the event loop in module-rtp-recv and elsewhere
> should be done through pa_mainloop_api instead of accessing the underlying
> implementation directly. This requires a pa_mainloop_api implementation
> based on pa_rtpoll.</span >
The intention behind the quoted paragraph was that we'd keep using pa_mainloop
in the tunnel modules and pa_rtpoll elsewhere. When I started to work on this,
I decided to go with a different approach: I changed the event loop
implementation in the tunnel modules to pa_rtpoll. That still required me to
implement pa_mainloop_api on top of pa_rtpoll, because libpulse requires
pa_mainloop_api. I've sent patches to the mailing list:
<a href="http://thread.gmane.org/gmane.comp.audio.pulseaudio.general/22563">http://thread.gmane.org/gmane.comp.audio.pulseaudio.general/22563</a></pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>