[Bug 54270] Don't run the TplLogEventFilter from a separate thread

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=54270

--- Comment #3 from Debarshi Ray <rishi.is at lostca.se> ---
The lock was used to serialize multiple calls get_events and rewind at a time
when both the async operations were implemented in a thread. Now only rewind is
done in a thread, but not get_events.

So you are correct that two successive calls to get_events will now cause
problems because it is not implemented in a thread anymore.

I was looking at using a queue to do the serialization now. So if you make the
following calls without returning to the main loop:
 - get_events
 - get_events
 - rewind
 - get_events
... they will be kept in the queue and executed in FIFO order one by one.

However I am wondering how we could hook into the completion of an operation
(eg., rewind which is done using g_simple_async_result_run_in_thread). When an
operation completes we want to check if there are pending operations in the
queue and if so, execute them.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.