<p><br>
On Sep 9, 2012 8:51 PM, "Nick Rout" <<a href="mailto:nick.rout@gmail.com">nick.rout@gmail.com</a>> wrote:<br>
><br>
> On Mon, Sep 10, 2012 at 12:08 PM, Jay Ashworth <<a href="mailto:jra@baylink.com">jra@baylink.com</a>> wrote:<br>
> > ----- Original Message -----<br>
> >> From: "Daniel Frey" <<a href="mailto:dmfrey@gmail.com">dmfrey@gmail.com</a>><br>
> ><br>
> >> The reason for requiring the data is to provide a search function that will<br>
> >> globally search the program guide so that you can manage your recordings<br>
> >> much like you would from mythweb. Just because you may not use this<br>
> >> functionality, does not mean someone else will not. Please keep in mind<br>
> >> this app will be another front end, not just a viewer. Please bare with us<br>
> >> while we work out this loading issue.<br>
> ><br>
> > Please let me call your attention to "client-server application design",<br>
> > the thing which SQL was,very roughly, invented to support.<br>
> ><br>
> > If you're yanking *the entire recorded programs directory* over the wire<br>
> > to the client, you badly need to refactor that code.<br>
><br>
> That was kinda the thought I had, but didn't want to appear rude or<br>
> ignorant (not saying you did either!). Also they are using the<br>
> services api to do as much as possible, not sure what search<br>
> facilities that provides?<br>
><br>
> Daniel, don't get us wrong, we appreciate what you are doing!<br>
><br>
><br>
> ><br>
> > My apologies if this seems peremptory; I rewrote it 3 or 4 times.<br>
> _______________________________________________<br>
> mythtv-users mailing list<br>
> <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
> <a href="http://www.mythtv.org/mailman/listinfo/mythtv-users">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br></p>
<p>Thanks Nick. You are correct, we are using the services api in Android. It allows us to load the data in the background. Also, the design pattern we use aims to minimize network activity (thus saving battery) by loading the data locally to a database and most interactions with the data are through the local database. It would be far too slow from a UI/UX standpoint to always be loading data from the backend on demand, and it would drastically affect battery. Loading the data to a local db allows us to provide a faster user experience. Albeit, the db load does take a long time to load and we are working on that. </p>
<p>Searching through programs, recordings, videos, etc will come later, once we get the db load more efficient. In order to implement a global search (like the YouTube app) we not only need to load the data to a database, but provide access via a Content Provider. Android may relax this requirement in the future, but for now, that is what we are stuck with. </p>
<p>Jay, we are not loading the entire db every time the app starts, it is only done the first time, and then in day increments. We then check daily and only add what's missing since your last mythfilldatabase run. Believe me, I have refactored this code numerous times to try to get it. The reason I block other activities is I don't want you trying to update other entries (recorded or upcoming) while the db is loading data. </p>
<p>I hope this gives a little more insight into our design and the reasons we did what we did. </p>
<p>I am open to suggestions if anyone sees issue with this. </p>
<p>Dan</p>