2010-10-06, 15:24
dteirney Wrote:Yes, it is a known problem that the Myth Protocol was changed to require a token that matches the requested version number of the protocol. Personally I'm not sure why it's needed<...>It is needed precisely because of what you describe next:
Quote:The ProgramInfo object returned changed a lot so libcmyth will need some time spent on it to get that sorted <...>I'm not a Myth dev, but I follow them pretty closely - and they most definitely do not have anything against libcmyth or similar concepts. In fact, they would like to see more of them. It is very simple: the token was added because if someone tries to use libcmyth in its current state, it will cause problems. That is the only reason that the devs "take a dim view" of it. The further behind something like libcmyth falls, the more problems it causes. Without the token to insure compatibility, people will encounter problems and continue to come (as they have in the past) to the MythTV community and claim there is a bug.
Marc