[mythtv] [PATCH] revised/added protocol extension patch -- ignore last one

Isaac Richards ijr at case.edu
Sun May 1 23:28:04 UTC 2005


On Sunday 01 May 2005 03:32 pm, Brad Templeton wrote:
> On Sun, May 01, 2005 at 01:45:01PM -0400, Noone wrote:
> > It is a step in the right direction imho.  Since the end result would
> > also be the backend caches much of the commonly requested data (recorded
> > list, guide data, ICONS, etc.), the hit shouldn't be that bad.
>
> I don't know about the insides of mysql, but surely it caches data of
> common queries, no?  And far better than an intermediate backend could do
> because the intermediate backend is not aware of possible writes to the
> data by other sources (including in some cases itself.)

Exactly.  mysql does a pretty good job of caching things properly, so repeated 
queries are damn quick - especially for simple stuff from the settings table.  
Doesn't make sense to me to recreate all that in the backend.  Might as well 
just write your own DB at that point.

> I remain curious on the strong goal here.  I mean yes, there can always
> be value in extra levels of abstraction, but your talking raw SQL
> and getting back only slightly modified query results so little abstraction
> is being added.
>
> Is it that sql query libraries are not available for some clients?  Is it
> that they are too expensive?  Is it that they are too hard to code for?

My questions as well, every time this is brought up.  libmysqlclient's just a 
cross-compile away for almost any platform.  It's tiny, too - if a platform's 
that starved for RAM, it's not going to be capable of displaying much of a 
UI, either.

Isaac


More information about the mythtv-dev mailing list