[mythtv] [PATCH] revised/added protocol extension patch -- ignore
ijr at case.edu
Mon May 2 16:42:31 UTC 2005
On Sunday 01 May 2005 10:05 pm, Kevin Kuphal wrote:
> Isaac Richards wrote:
> >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.
> Just out of curiosity, do you see any benefit in terms of feature
> "portability" in having these functions (other than the generic SQL)
> present in the backend so that they can be reused by all the frontends
> (mythfrontend, mythweb, mediaMVP, mythroku) so that when code is added,
> enhanced, fixed, or changed, all the frontends can implement it using
> identical calls rather than individual efforts possibly prone to errors?
Right. There's some benefit to that, I'm just not sure if it's worth the
extra time those queries would then take, especially if the frontend were
made to use 'em.
Although, one _could_ also argue that other projects should just use
libmyth/libmythtv instead of reimplementing things from scratch, too.
Granted, the requirements are slightly heavy for tiny systems, but there's a
reason that those things are in libraries in the first place.
More information about the mythtv-dev