GstInterpipe - Caps Negotiation: Difference between revisions

From RidgeRun Developer Wiki
No edit summary
mNo edit summary
Line 1: Line 1:
{{GstInterpipe Page|  
{{GstInterpipe/Head |previous=Dynamic Switching|next=Event Forwarding|keywords=}}
[[GstInterpipe - Dynamic Switching|Dynamic Switching]]|
[[GstInterpipe - Event Forwarding|Event Forwarding]]|


This page contains a detailed description of the GstInterpipe '''Caps Negotiation''' feature.  
This page contains a detailed description of the GstInterpipe '''Caps Negotiation''' feature.  
Line 11: Line 9:
[[File:Caps_negotiation.png|600px|framed|center|Caps negotiation process]]
[[File:Caps_negotiation.png|600px|framed|center|Caps negotiation process]]


}}
{{GstInterpipe/Foot|previous=Dynamic Switching|next=Event Forwarding}}

Revision as of 10:19, 9 April 2020




Previous: Dynamic Switching Index Next: Event Forwarding




This page contains a detailed description of the GstInterpipe Caps Negotiation feature.


GstInterpipe takes into account the node and all its listeners during the caps negotiation process. It is guaranteed that the resulting supported set of caps will be an intersection between all the listeners and node caps. This only applies to the listeners that are connected during the caps negotiation process. If a listener is adhered later, it will be handled independently (see Dynamic Switching).

The following figure shows this concept.

Caps negotiation process


Previous: Dynamic Switching Index Next: Event Forwarding