----- Original Message -----
From: Ronald Bultje <rbultje@...>
Date: 30 Jun 2003 09:23:19 +0200
To: Cyrius <suiryc@...>
Subject: Re: [gst-devel] Fwd: Re: [UCI-Devel] Re: [matroska-devel] Re: Common Opensource codec API
> On Sun, 2003-06-29 at 02:38, Cyrius wrote:
> > See I think the different operations like filters
> > and muxing should just be subsets of the message
> > space.
> This was my idea exactly. The muxing/codec operation subsets themselves
> should be described in the protocol, too, but shouldn't introduce any
> new features or methods, they should just implement a specific way of
> using the generalized methods for their specific task.
> > One of the reasons I was advocating a system with
> > 2-way communication at each level was to do things
> > like have an app request an operation that a filter
> > does not support, and have the filter propose an
> > alternate operation by calling back other parts of
> > the system for more info. Thus programmers would be
> > free to do what they think is best for their code to
> > serve each message request.
> Let's first keep it simple. ;).
> Ronald Bultje <rbultje@...>
The main idea was to keep it simple. The problem is when you make everything one-way like VFW it becomes not simple to do certain things. I had simplicity as the main goal in mind when thinking this through.
Sign-up for your own FREE Personalized E-mail at Mail.com