[mythtv-users] ensuring mythbackend will be idle for db optimize

Jerome Yuzyk jerome at supernet.ab.ca
Mon Sep 28 18:07:34 UTC 2015


On Saturday, September 26, 2015 05:42:53 PM Philip Brady wrote:
> 
> > Interesting module. Why do you not use an XML parser? I have to live with hand-rolled XML parsers in modules I use for work, and I happened to find the upcoming_recordings.pl example first and was relieved to see it use a known (though old) parser module so that was my model. Plus a way to learn how to use perl-XML for the future.
> > 
> > But, I gotta say, your tech support is great! :) I'm looking though the update now. Will try it this evening.
> > 
> > -- 
> Why not a standard parser?  SAX looked understandable but seemed to need a complex call stack to be maintained, and I honestly couldn't understand the other parsers!  They also looked as if they had high memory overheads.  That was my reasoning but I'm probably way off target!Would you like to give a simple example of using an XML parser for the wiki?
> On another wiki issue, do you have any views on where effort is most needed with the API pages?

Makes sense - for the limited domain the API covers a general-purpose parser may be overkill. Your method is very tight. I will tinker with a couple of the most-common modules though, to make some examples. The only reason I used XML::Simple is that https://www.mythtv.org/wiki/Upcoming_Parse.pl uses it and it was my first example. 

Is scan_database.pm going to become part of the distribution like MythTV.pm is?

https://www.mythtv.org/wiki/Frontend_Service needs to be fixed/updated to match the XML return that 0.27.4 (and maybe earlier) gets. That threw me off for a while. I assume the Wiki shows the 0.25 return and then the structure was changed to match that of the other services because it's the only one that's different. 

One thing I would like to do is make a summary page of the various ways that one can interact with Myth programmatically with Perl, because there are 4 ways that I can count: the Services API, WDSL, FE Control Socket, and MythTV.pm. I have not seen a collector page anywhere on the Wiki. There are lots of examples to tie together. 

I could contribute my WillBeQuiet script to the examples pile, after some more work. It's a niche function, but collects a few things together that aren't elsewhere, and could be of interest to anyone who uses their (FE/)BE machine for other things.

I can't say I understand enough at the moment to promise more, but as winter descends and nights grow longer I will learn more and would like to contribute. I kept the "Help with Documentation" thread from July for when I could see I'd have something to contribute, because I owe a lot to what's there already. 

-- 
A little of Jerome's MythTV World: http://mythtv.bss.ab.ca


More information about the mythtv-users mailing list