Original commit message from CVS:
Antoher way of dealing with EOS. This proposal does not use the recursion
to propagate the EOS signal. This implies that an element cannot deny an
EOS signal anymore but since the signal is generated when a NULL buffer is
pushed, somebody did something wrong anyway.
Original commit message from CVS:
While typing on eos2 about the EOS handling, I got an idea and started
eos3. eos3 takes a different approach by merging the eos detection and
the scheduling in a quite elegant way. I'm not sure we handle the
scheduling like this though...
