GStreamer Daemon - GStreamer Daemon Basics

From RidgeRun Developer Wiki
Revision as of 17:45, 15 May 2017 by Mgruner (talk | contribs) (Created page with "{{Gstd-1.0 Page | Building GStreamer Daemon| TODO| GStreamer Daemon is, as it name states, a process that runs independently and expo...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

{{Gstd-1.0 Page | Building GStreamer Daemon| TODO| GStreamer Daemon is, as it name states, a process that runs independently and exposes a public interface for other processes to communicate with and control it. The goal behind Gstd-1.0 is to abstract much of the complexity of writing custom GStreamer applications, as well as factoring out lots of boilerplate code required to write applications from scratch. As such, clients can focus on application-specific code accelerating time-to-market.

This public interface is exposed as different IPC (Inter Process Communication) mechanisms. Different products or applications will use the IPC of its most convenience. For example, QT applications may find it easier to communicate with Gstd-1.0 via DBus by autogenerating the respective bindings, web pages may find it natural to communicate via HTTP requests and desktop test frameworks may leverage the built-in TCP client distributed with the project.

In the current version, only TCP is supported.

The design behind GStreamer Daemon attempts to follow a MVC architecture. Figure 1 shows a high level diagram of the design: