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

[<bug...@wi...>]

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 rb...@ro....

--- shadow/123237	Tue Sep 30 06:52:54 2003
+++ shadow/123237.tmp.16438	Tue Sep 30 07:06:44 2003
@@ -61,6 +61,18 @@
 Another way to get around this is to change the API to not allow 
 getting request pads but automatically create request pads for 
 example via
 gst_element_request_link (element_to_link_to, pad_to_link_to, 
 pad_template_to_use_or_NULL)
 thought that would make it somewhat harder to link 2 request pads.
+
+------- Additional Comments From rb...@ro...  2003-09-30 07:06 -------
+I'd say it differently. For ALWAYS/SOMETIMES, you're correct, the
+elements owns them, controls them and destroys (or, rather, unrefs) them.
+
+For REQUEST, however, I'd say that the requester (application) owns
+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?