[mythtv-users] mythtv dropping mysql???
Michael T. Dean
mtdean at thirdcontact.com
Tue Oct 21 02:05:42 UTC 2014
On 10/20/2014 09:39 PM, Ronald Frazier wrote:
>
> IMHO, the biggest problem with providing easy access to the
> underlying, internal-use data is that it provides a means by which
> people can selfishly solve problems for themselves rather than
> helping to solve the problem for everyone.
>
>
> So is that your promise that any feature someone unselfishly develops
> will get incorporated into mythtv? Please, don't answer...obviously
> the answer is no, but that's exactly the point. Sometimes people do
> things to solve problems that nobody else really even cares about
> (because, for them, it's not a problem).
No, those things that should be incorporated will. Those "just makes
sense for me/a few/..." things will live in scripts (using the Python
bindings or Perl/Ruby/Java/(or even)sh with curl or wget processing XML
from the Services API or HTML from the backend web server). And since
the bindings, Services API, backend web server will be updated for
changes to data formats and interpretation, those scripts will be far
more robust--and safer for everyone.
Mike
More information about the mythtv-users
mailing list