[Bug 766898] player: Add a message queue API in addition to the signals

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=766898

--- Comment #21 from rland <rlandjon at gmail.com> ---
 for people who want to
> manage the bus life-cycle themselves, if for some reason they want to
> desychronize player instance and bus-reading-process lifecycles.

Managing two references, perhaps not sensible way, is just to illustrate a
"problematic snapshot" that is not circumvented by API design.I don't think of
any scenes that really need to hold references to two objects at the same
time.:)


>Therefore we should probably rather encapsulate all the bus methods needed by >API users. So wrap the pop call into a gst_player instance method. That will >avoid to be able using the bus if the instance is gone in the first place, and >per se rather require to use the player instance ref only.

Yeah,maybe this will make the user's life better. :)
After all, the real purpose of the user is to safely get the asynchronous
message from the api_bus and handle it without thinking about more multi-thread 
 synchronization across modules.

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