[gst-devel] Decoupled elements and schedulers

[Martin Soto]

On Tue, 2004-03-30 at 22:31, David Schleef wrote:
> On Tue, Mar 30, 2004 at 07:24:08PM +0200, Martin Soto wrote:
> > I see two ways out of this. Either you forbid an element with a loop to
> > also have chains and gets, or, at least, you make clear that the chains
> > and gets won't be run if there's a loop.
> 
> This is already the case.  Some of the core element have both loop
> and chain functions, but only as a legacy.  No real element would
> ever bother, because it leads to code paths that are nearly
> impossible to test, thus leading to bugs that only users will ever
> see.

Right. I've been thinking of it, and that looks like a pretty resonable
policy: if an element has a loop, it is used and chains and gets are
ignored.

M. S.
-- 
Martin Soto <soto at informatik.uni-kl.de>
Universität Kaiserslautern