<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
On 4/18/2008 1:02 AM, Michael T. Dean wrote:
<blockquote cite="mid:4808395C.3080705@thirdcontact.com" type="cite">
<pre wrap="">On 04/17/2008 05:29 PM, Robert Eden wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Another thing. I (personally) consider the default MythTV fetch
behavior is broken. (Today, Today+14). By default, all guide data
except for today is 14 day advance data. I think expecting (correct)
details 14 days ahead is too much to ask. A better compromise is Today,
+1, +2, +7, +14
</pre>
</blockquote>
</blockquote>
.....<br>
<blockquote cite="mid:4808395C.3080705@thirdcontact.com" type="cite">
<blockquote type="cite">
<pre wrap="">It would also be nice if Myth could grab in larger than 1-day chunks,
but that's just a system load issue.
</pre>
</blockquote>
<pre wrap=""><!---->
Though doing so with your recommended fill behavior would only be
beneficial for today and +1, right?
</pre>
</blockquote>
No... let's say you want Today, +1, +2, +7, +14<br>
You could make 3 grabs ( +0, +1, +2), +7, +14 rather than 5 grabs.<br>
<br>
Of course the big gains come from a --refreshall (which makes 14 calls
at the moment)<br>
<br>
The larger chunks are more efficient to generate and transfer, but may
place a large memory burden on the client when it combines the data,
especially with large lineups. Maybe a middle-ground could be found. <br>
<br>
Setting the HTTP agent string would also be polite BTW... include the
MythTV and grabber version.. it can help with troubleshooting.<br>
<br>
Robert<br>
</body>
</html>