[gstreamer-bugs] [Bug 123237] REQUEST pad lifecycle needs documentation, element utils need corresponding updates

[bugzilla-daemon at bugzilla.gnome.org]

Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=123237
 GStreamer | gstreamer (core) | Ver: HEAD CVS

wingo at pobox.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[API] need policy for       |REQUEST pad lifecycle needs
                   |disappearance of SOMETIMES  |documentation, element utils
                   |and REQUEST pads            |need corresponding updates



------- Additional Comments From wingo at pobox.com  2005-07-14 16:16 -------
If an automatic linking functions (i.e. gst_element_link_pads()) request a pad,
they should connect to ::unlinked on the request pad. The onus (I just said
onus) is on the immediate caller of gst_element_request_pad to arrange to
release the request pad.

Parent objects always have references to their children. Thus removing the
application's reference is insufficient to dispose the pad. release_request_pad
must be used as Wim said. Leaving bug open until docs are updated
(docs/manual/basics-pads.xml) and the gstutils functions arrange to release the
request pad (preferably accompanied by test suites). Changing name to reflect
nature of bug. 

------- You are receiving this mail because: -------
You are the assignee for the bug.
You are the QA contact for the bug.