<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 4/11/2012 18:25, Oliver Maunder wrote:
<blockquote
cite="mid:CALYkhrc3SNT0-X1RWQp9Jnq8PqQx4tZcV6Zeivn6pHmRq7-nqg@mail.gmail.com"
type="cite">
<div>On 11 April 2012 22:29, jacek burghardt <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:jaceksburghardt@gmail.com">jaceksburghardt@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote"
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I
hope there is someone that can point me in right direction
xbmc<br>
handles few thinks better then mythfrontend<br>
</blockquote>
</div>
<br>
<div>Looking at the XBMC source code, the most recent Myth
protocol version supported is 64. 0.24 uses version 63 and 0.25
uses version 64.</div>
</blockquote>
<br>
No. 0.25 uses version 72.<br>
<br>
<blockquote
cite="mid:CALYkhrc3SNT0-X1RWQp9Jnq8PqQx4tZcV6Zeivn6pHmRq7-nqg@mail.gmail.com"
type="cite">
<div>However, according to the <a moz-do-not-send="true"
href="http://www.mythtv.org/wiki/Category:Myth_Protocol">Myth
Protocol wiki page</a>, XBMC implements the Myth protocol
version badly - which essentially means that it will pretend to
support a more recent version than it really does. As the wiki
says - "<span
style="font-family:sans-serif;font-size:13px;line-height:19px;background-color:rgb(255,255,255)">This
should be considered very dangerous behavior, and should not
be used to connect to any production backend."</span></div>
</blockquote>
<br>
The MythBox plugin implements the protocol properly. However, the
MythBox plugin only implements a content list, and points XBMC at
what content to actually play. XBMC in turn uses the libcmyth
implementation which blindly parrots back the version mythbackend
speaks. Starting with protocol version 62, this no longer works, as
the backend will refuse connection to anything using the wrong token
for that version number, forcing applications to actually update
themselves to support new protocol versions.<br>
<br>
Last I heard, both libcmyth and MythBox were deprecated by some new
built-in PVR support, intended to allow access to MythTV, TVHeadend,
VDR, or any other recording backend. I do not know the current
state of development of that replacement.<br>
<br>
<blockquote
cite="mid:CALYkhrc3SNT0-X1RWQp9Jnq8PqQx4tZcV6Zeivn6pHmRq7-nqg@mail.gmail.com"
type="cite">
<div><font face="sans-serif"><span style="line-height:19px">It
looks like XBMC generally queries the MySQL database
directly, rather than making requests via the Myth protocol,
so the protocol version it supports might not matter than
much. Of course, if the database structure has changed then
there could be problems.</span></font></div>
</blockquote>
<br>
At the moment, there are many things that simply require direct
database access to accomplish. The intent is that all such
mechanisms be removed prior to 0.27, to allow the migration to an
embedded MySQL database that the backend has full control over.
Beyond that point, all communication will have to be performed
through the backend protocol, or more likely through the new
Services API.<br>
<br>
</body>
</html>