[mythtv-users] [old] Re: XvMC and libmpeg2 to be dropped in 0.25

[Svend Høst]

2011/2/9 Ryan Patterson <ryan.goat at gmail.com>

> On Wed, Feb 9, 2011 at 6:46 AM, Brian J. Murrell <brian at interlinx.bc.ca>
> wrote:
> > My comment was that that it's impossible to leave one (say) FE in a myth
> > network at a version that works well for it and provides the needed
> > hardware support when you need to upgrade another machine in the myth
> > network to get hardware support for newer hardware simply because one
> > has to always upgrade all machines due to myth refusing any sort of
> > back/for-ward protocol compatibility.
>
> Yes you have to choose one version of MythTV for your entire network
> of frontends and backends.  That seems to only make sense.  Can you
> swap a different design of engine block into your car without also
> changing the heads and manifolds?  No, all those things must match
> each other.
>

I'm not a myth developer myself, only a developer. In my prof. life i did a
client/server application where the server was backwards compatible with
clients from first release, also in the fourth release. Off course the
client's only knew off functionality that there was present with there
corresponding release.

I'm not sure what the diffs are in the protocol between .24 and .25, and
maybe there is a valid reason for being rigid (using Brians words). But
chances are that if this was a key issue for the developers, they could make
it work.

Off course it is more difficult to go the other way around with older
servers and newer clients, but making a newer server understand an older
client is feasible in many projecs.



> -Ryan
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20110209/c56b26c2/attachment.htm>