[mythtv] Ticket #4956: Make MythXML's GetProgramGuide return shows inclusively

Michael T. Dean mtdean at thirdcontact.com
Tue Jul 8 20:04:57 UTC 2008

On 07/08/2008 03:35 PM, Chase Douglas wrote:
> On Jul 8, 2008, at 3:17 PM, Michael T. Dean wrote:
>> Even if it's applied immediately, it likely won't go to -fixes,  
>> meaning
>> it won't be available "to the general public" until the 0.22 release.
> I don't follow the development of mythtv too closely, but wouldn't  
> this be the type of fix that would be intended for the -fixes branch?  
> If not, what types of fixes are meant for that branch.

The issue is that the current behavior isn't really "broken"--it just 
works a bit differently from how one might expect (and differently from 
how the Myth protocol works).  I think when David Blain originally wrote 
the code, he felt it was better for the "server" to trim out the extras 
for the (possibly low-powered/low-resource) client rather than send 
excess info (though he agreed in IRC to change it to make it symmetrical 
with GuideGrid::GetProgramList() ).

So, to support the "old" approach, you can use the "summary" version of 
the listings to get information about a range of times that's larger 
than the listings to be displayed (i.e. perhaps an hour before and after 
the displayed times) and, for channels with missing data, go even 
farther back/forward for that particular channel as necessary to fill in 
the blanks.  And, if you need details for all shows, you can then use 
the data from the summary to make the exact request you need on a 
per-channel basis.

See http://www.gossamer-threads.com/lists/mythtv/dev/323174#323174 (and 
the rest of the thread) for a bit more info on using GetProgramGuide.

>> That means if you want to write a client that's usable by 0.21(-fixes)
>> users, you'd have to write it to work with the "old" approach (and
>> support the "new" approach once available).  If you're writing a  
>> client
>> for yourself, you can simply apply the patch to your own tree  
>> (though I
>> haven't tried lately, it should apply cleanly to either -fixes or  
>> trunk).
> I'm not writing a normal client. In fact, I don't use the mythtv  
> protocol at all. The reason I use the MythXML interface is because it  
> does not require any authentication or server setup (compared to  
> looking it up in the mysql db) and it does not require a mythtv  
> protocol match.

Yeah, you're actually doing things the right way.  Unfortunately, you 
just happen to be pretty much the first person to do it the right way, 
so you get to experience the growing pains as the XML interface catches 
up with "the real world."

>> Also, if you send an iPhone (based on your link to
>> http://trac2.assembla.com/mymote ) to Greg Estabrooks (the current  
>> owner
>> of the ticket), he may actually find this ticket to be higher priority
>> once he receives it.  :)
> If only I had that kind of money...



More information about the mythtv-dev mailing list