[gst-devel] GDP updates and questions

Michael Smith msmith at fluendo.com
Wed May 10 01:01:39 CEST 2006


On Tue, 2006-05-09 at 13:03 -0700, David Schleef wrote:
> On Tue, May 09, 2006 at 08:29:40PM +0200, Thomas Vander Stichele wrote:
> > Strictly speaking this would be an ABI change; however, nothing in
> > GStreamer actually serializes events at the moment.  The question is,
> > which of the following is preferred:
> > 1) changing it without revving the GDP major/minor version
> > 2) changing it, revving the major/minor, thus making it so older core
> > cannot use GDP with newer core processes
> > 3) changing it, revving, and implementing fallback code for the older
> > GDP version
> 
> I think what you actually mean is:
> 
> 1) changing it without revving the GDP major/minor version, thus making
> it so older core communicating with newer core *breaks in non-intuitive
> ways*.

Well, more specifically still, making it so that ALL ZERO of the
applications using GDP event serialisation/deserialisation break in
non-intuitive ways when they have different core versions on either
side. 

Metaphysical Question: if some API that has never been used by any
applications, tests, or examples, is broken, did it really break at all?
See also: bears shitting in the woods, etc.

Mike






More information about the gstreamer-devel mailing list