[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 #6 from Stephan Hesse <tchakabam at gmail.com> ---
Understood, makes sense.

So then the idea would be: 

- position, duration and other values of arbitrary/transient character can be
queried from the API at any moments

- messages get created with data that is queried on creation of the message
from within the pipeline, using the exact same mechanism as the corresponding
API methods (to read position/duration etc)

Will add some custom functions to create those position/duration messages with
the values obtained from the pipeline instead of caching them (as for error and
warning).

We may still be able to use the current _from_state method for messages that
actually can get created from the state solely.

And our next step would now be (re)moving the signal stuff from this file and
building a proxy object from signal-based API as you had suggested. 

We probably also need to think about how to deal with an application that would
not consume from the bus, how to avoid filling memory with more and more data
structures that are not being consumed/unrefed at some point. Maybe I am still
a bit unfamiliar with GstBus. How is this usually done?

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