20,290
edits
GstWebRTC - Custom Signaling: Difference between revisions
m
no edit summary
mNo edit summary |
mNo edit summary |
||
| Line 6: | Line 6: | ||
==Custom | ==Custom Signaling Basics== | ||
Custom signalers are implemented by subclassing the GstBaseSignaler class. By doing so, the new signaler is integrated into GstRrWebRTC state machine logic. The diagram in Figure 1 summarizes the concept: | Custom signalers are implemented by subclassing the GstBaseSignaler class. By doing so, the new signaler is integrated into GstRrWebRTC state machine logic. The diagram in Figure 1 summarizes the concept: | ||
| Line 12: | Line 12: | ||
[[File:gstwebrtc-uml-signaler.png|800px|center|Figure 1. UML Diagram of Concrete Signalers]] | [[File:gstwebrtc-uml-signaler.png|800px|center|Figure 1. UML Diagram of Concrete Signalers]] | ||
==Integrating a Custom | ==Integrating a Custom Signaling== | ||
There are two ways a custom signaler can be integrated into the project. The first one is to build the new signaler along with the GstRrWebRTC project. In this case the signaler will be part of the project's binaries and the signaler's properties will be shown in the inspect output. The second way to integrate an external signaler is by doing it at runtime via the '''signaler-obj'''. In this case the signaler is built in an independent project and passed to the WebRTC state machine at runtime. The following subsections present further details. | There are two ways a custom signaler can be integrated into the project. The first one is to build the new signaler along with the GstRrWebRTC project. In this case the signaler will be part of the project's binaries and the signaler's properties will be shown in the inspect output. The second way to integrate an external signaler is by doing it at runtime via the '''signaler-obj'''. In this case the signaler is built in an independent project and passed to the WebRTC state machine at runtime. The following subsections present further details. | ||