Difference between revisions of "Protocol change"

From MythTV Official Wiki
Jump to: navigation, search
(Undo revision 44885 by Yvonne80 (Talk) spam, spam, spam, spam, spam, bacon, eggs, spam, and spam)
m (shift link)
Line 1: Line 1:
Changes to the MythTV communications [[protocol]] require a change to the protocol version.  This is most commonly noticed when running different versions of a [[backend]] and [[frontend]].  MythTV does not support running different protocol versions between a [[client]] and [[server]].   
+
Changes to the MythTV communications [[protocol]] require a change to the protocol version.  This is most commonly noticed when running different versions of a [[Mythbackend]] and [[frontend]].  MythTV does not support running different protocol versions between a [[client]] and [[server]].   
  
 
If you experience a protocol mismatch, you need to be sure all your systems are running the same version of the software.  If you are using a [[development branch]] like [[trunk]] or the fixes branch, be sure your systems are all running the same [[revision]] of the software as the protocol version can change within a development branch before an official release [[tarball]] is made.
 
If you experience a protocol mismatch, you need to be sure all your systems are running the same version of the software.  If you are using a [[development branch]] like [[trunk]] or the fixes branch, be sure your systems are all running the same [[revision]] of the software as the protocol version can change within a development branch before an official release [[tarball]] is made.

Revision as of 20:36, 12 March 2011

Changes to the MythTV communications protocol require a change to the protocol version. This is most commonly noticed when running different versions of a Mythbackend and frontend. MythTV does not support running different protocol versions between a client and server.

If you experience a protocol mismatch, you need to be sure all your systems are running the same version of the software. If you are using a development branch like trunk or the fixes branch, be sure your systems are all running the same revision of the software as the protocol version can change within a development branch before an official release tarball is made.

Many package maintainers (rpm, deb, ebuild) build packages from the fixes branch. This means that they are distributing an unreleased version of the software. Official releases are distributed from www.mythtv.org as a download.