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

Original commit message from CVS:
* docs/design/part-TODO.txt:
Add another limitation of pad-blocking with segment seeks not pushing
EOS events.

diff --git a/ChangeLog b/ChangeLog
index 12c939a..8925c4d 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -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>
 
        * win32/common/libgstbase.def:

diff --git a/docs/design/part-TODO.txt b/docs/design/part-TODO.txt
index 9737ee9..ed1c356 100644 (file)
--- a/docs/design/part-TODO.txt
+++ b/docs/design/part-TODO.txt
@@ -71,6 +71,8 @@ API/ABI
     reason that blocked the pad. 
   * 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.
+  * 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
     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