[Bug 735357] pad: should not allow flush-stop on inactive pads

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=735357
  GStreamer | gstreamer (core) | git

Thiago Sousa Santos <thiagossantos> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |

--- Comment #4 from Thiago Sousa Santos <thiagossantos at gmail.com> 2014-09-12 00:05:10 UTC ---
This bug seems to make an use case harder, I propose the above patch instead of
it.

The use case is in adaptive demuxers to restart the http source for downloading
a new fragment after it has gone EOS.

1) The httpsrc finishes downloading and pushes EOS
2) EOS is intercepted and dropped in some pad downstream
3) The elements are put to READY, the src is put to NULL and gets a new URI
4) src is brought back to READY
5) A flush-start/stop pair is sent on this branch to remove the EOS status of
the elements.

Does this make sense? The other options I have are to put all the elements in
the branch to NULL or iterate over the pads and clear the flag by
deactivating/activating them.

Reopening the bug so we can discuss this.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.