<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 18, 2014 at 3:33 PM, Tom Dexter <span dir="ltr"><<a href="mailto:digitalaudiorock@gmail.com" target="_blank">digitalaudiorock@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Sep 18, 2014 at 1:33 PM, Robert Kulagowski <<a href="mailto:rkulagow@gmail.com">rkulagow@gmail.com</a>> wrote:<br>
> The instructions at<br>
><br>
> <a href="https://github.com/SchedulesDirect/mfdb-json/tree/API-20140530" target="_blank">https://github.com/SchedulesDirect/mfdb-json/tree/API-20140530</a><br>
><br>
> are a little clearer (hopefully) and have additional information.<br>
<br>
</span>Wow...I'm definitely going to sit this one out until I hear more<br>
specifics from the MythTV side of things on all this. I don't really<br>
have time to dig into the stuff explained there in detail right now,<br>
but I'm not even sure I understand what's needed for this at a high<br>
level. For example, if it can use existing lineups or if you have to<br>
create a new one, or if it requires stuff like a new input connection<br>
(sounds like it does??). Yuk.</blockquote><div><br></div><div>The way I read it, the XML service will remain functional, however data will only get updated once a day from the JSON feed. If I am interpreting things correctly, we won't really be impacted... however the JSON solution offers significant incentive to transition so I would expect that an update to mythfilldatabase will follow closely behind the transition.</div><div><br></div><div><br></div></div></div></div>