mirror of
https://gitlab.freedesktop.org/gstreamer/gstreamer.git
synced 2025-04-26 04:46:13 +00:00
manual: fix another typo and some inaccuracies
Fix a wrong statement and flesh out section on messages and queries a bit.
This commit is contained in:
parent
80ece8a4be
commit
8bfc2cc0c8
1 changed files with 16 additions and 10 deletions
|
@ -108,32 +108,38 @@
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<emphasis>buffers</emphasis>: are objects for passing streaming data
|
<emphasis>buffers</emphasis> are objects for passing streaming data
|
||||||
between elements in the pipeline. Buffers always travel from sources
|
between elements in the pipeline. Buffers always travel from sources
|
||||||
to sinks (downstream).
|
to sinks (downstream).
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<emphasis>events</emphasis>: are objects send between elements or from
|
<emphasis>events</emphasis> are objects sent between elements or from
|
||||||
the application to elements. Events can travel upstream and downstream.
|
the application to elements. Events can travel upstream and downstream.
|
||||||
Downstream events can be synchronised to the data flow.
|
Downstream events can be synchronised to the data flow.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<emphasis>messages</emphasis>: are objects send from elements over the
|
<emphasis>messages</emphasis> are objects posted by elements on
|
||||||
bus to the application. Messages can be received synchronously, but
|
the pipeline's message bus, where they will be held for collection
|
||||||
then from the streaming thread context of the sender or asynchronously
|
by the application. Messages can be intercepted synchronously from
|
||||||
marshalled to the main thread of the application.
|
the streaming thread context of the element posting the message, but
|
||||||
|
are usually handled asynchronously by the application from the
|
||||||
|
application's main thread. Messages are used to transmit information
|
||||||
|
such as errors, tags, state changes, buffering state, redirects etc.
|
||||||
|
from elements to the application in a thread-safe way.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
<emphasis>queries</emphasis>: allow application to request information
|
<emphasis>queries</emphasis> allow applications to request information
|
||||||
from the pipeline. Queries are answered synchronously. Also elements
|
such as duration or current playback position from the pipeline.
|
||||||
can use queries. They can be used both ways, but most common are
|
Queries are always answered synchronously. Elements can also use
|
||||||
downstream queries.
|
queries to request information from their peer elements (such as the
|
||||||
|
file size or duration). They can be used both ways within a pipeline,
|
||||||
|
but upstream queries are more common.
|
||||||
</para>
|
</para>
|
||||||
</listitem>
|
</listitem>
|
||||||
</itemizedlist>
|
</itemizedlist>
|
||||||
|
|
Loading…
Reference in a new issue