[gst-devel] requested pads

[Benjamin Otte]

The agreed on method about how it's supposed to work was:
- ALWAYS pads exists as long as the element exists (the element keeps a
reference)
- SOMETIMES pads exist as long as the elements want. They might go away
without warning. Only the element should keep a reference. Note that the
element removing the pad means automatic unlinking.
- REQUEST pads exist as long as someone keeps a reference to it. The
element itself doesn't keep a reference. Normally the only reference is
the peer pad, so the pad goes a way when unlinking.

Unfortunately "supposed to work" != "how it works", so expect bugs there.

Benjamin


On Sat, 24 Jan 2004, Julien MOUTTE wrote:

>
> GstElement provides a release_pad method so that elements with requested
> pads can handle them correctly.
>
> It seems that nobody is currently implementing that method in elements
> supporting requested pads.
>
> Moreover when unlinking elements like tee for example pads are just
> leaked.
>
> Why not implementing in gst_pad_unlink something that would
> gst_element_release_request_pad if the pad was requested ?
>
> I m already implementing a release_pad method in switch so that switch
> is keeping it's internal pads list accurate.
>
> thoughts ?
>
> --
> Julien MOUTTE (aka Dolphy)
>
> Homepage : http://dolphy-tech.net
>