[Gstreamer-bugs] [Bug 123237] Changed - need policy for disappearance of SOMETIMES and REQUEST pads

[bugzilla-daemon at widget.gnome.org]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

http://bugzilla.gnome.org/show_bug.cgi?id=123237

Changed by in7y118 at public.uni-hamburg.de.

--- shadow/123237	Tue Sep 30 07:06:44 2003
+++ shadow/123237.tmp.13898	Tue Sep 30 09:41:29 2003
@@ -73,6 +73,23 @@
 the pad, not the element. So the application must also unref it when
 it's done. This also means that for each request pad, the element gets
 an additional ref() and the element is unref()ed when the pad is
 destroyed.
 
 Does that make sense?
+
+------- Additional Comments From in7y118 at public.uni-hamburg.de  2003-09-30 09:41 -------
+I don't like that idea, because most of the time the app doesn't want 
+to know that it just linked request pads and now is responsible for 
+them. gst_element_link makes use of request pads for example.
+
+But after thinking a bit more about it I think it makes sense to sink 
+a request pad when it is linked and make the element not hold a 
+reference to it. That way the only reference is held by the peer pad 
+(unless the application refs the pad before) and the pad is removed 
+automatically upon unlinking.
+
+So in short:
+ALWAYS: element/peerpad hold references.
+SOMETIMES: element/peerpad hold references, element might unlink and 
+remove.
+REQUEST: peerpad holds reference, element does not.