[mythtv] Backwards compatibility

[Stuart Auchterlonie]

On 07/01/16 16:38, Lawrence Rust wrote:
> On Thu, 2016-01-07 at 09:17 -0500, Dan Wilga wrote:
>> On 1/7/16 4:24 AM, Lawrence Rust wrote:
>>> I don't want to re-invent the wheel so I'd like to use an existing
>>> lightweight RPC mechanism (something that doesn't use JSON or XML
>>> etc). The Myth protocol, although clunky, looks as if it better fits
>>> those requirements. I'm not familiar with the services API but at 1st
>>> looks it appears to have much higher overhead and latency. Please
>>> correct me if I'm mistaken...
>>
>> IIRC, Myth already uses ZeroMQ in places. Perhaps that would be a good 
>> way to do the communication? It has less overhead than anything HTTP-based.
> 
> Yes, 0MQ would be a good candidate to replace the basic Myth protocol.
> But I don't believe it provides data serialisation.  So it would need
> something like Google's 'Protocol Buffers' on top.
> 

It's also part of the logserver which has been disable for 0.28.

So if we want it it needs surgically separating from the logserver
and the nzmqt (qt interface for 0mq) needs updating.

I have a vague recollection of issues with nzmqt before.


Regards
Stuart Auchterlonie