docs/design/part-TODO.txt: Add another limitation of pad-blocking with segment seeks not pushing

Original commit message from CVS:
* docs/design/part-TODO.txt:
Add another limitation of pad-blocking with segment seeks not pushing
EOS events.
This commit is contained in:
Edward Hervey 2008-10-10 14:31:03 +00:00
parent e5c6463d28
commit 6bb3d02305
2 changed files with 8 additions and 0 deletions

View file

@ -1,3 +1,9 @@
2008-10-10 Edward Hervey <edward.hervey@collabora.co.uk>
* docs/design/part-TODO.txt:
Add another limitation of pad-blocking with segment seeks not pushing
EOS events.
2008-10-10 Jan Schmidt <jan.schmidt@sun.com> 2008-10-10 Jan Schmidt <jan.schmidt@sun.com>
* win32/common/libgstbase.def: * win32/common/libgstbase.def:

View file

@ -71,6 +71,8 @@ API/ABI
reason that blocked the pad. reason that blocked the pad.
* it only blocks on datapassing. When EOS, the block never happens but ideally * it only blocks on datapassing. When EOS, the block never happens but ideally
should because pad block should inform the app when there is no dataflow. should because pad block should inform the app when there is no dataflow.
* the same goes for segment seeks that don't push in-band EOS events. Maybe
segment seeks should also send an EOS event when they're done.
* blocking should only happen from one thread. If one thread does pad_alloc * blocking should only happen from one thread. If one thread does pad_alloc
and another a push, the push might be busy while the block callback is done. and another a push, the push might be busy while the block callback is done.
* maybe this name is overloaded. We need to look at some more use cases before * maybe this name is overloaded. We need to look at some more use cases before