Re: names for SD-JSON grabbers (tv_grab_sd_json, tv_grab_na_sd)
Kevin Groeneveld <[email protected]>
| Newsgroups | gmane.comp.tv.xmltv.devel |
|---|---|
| Message-ID | <CABF+-6Wb1B8MZJZNky37paKBW05hFZTe6Z8Ccakq17H3WTpMbQ@mail.gmail.com> |
On Sat, Jul 23, 2016 at 4:46 AM, Geoff <[email protected]> wrote: > On Fri, 22 Jul 2016 15:25:37 -0500, Robert Eden wrote: > > I'm thinking the path of least resistance is keep tv_grab_sd_json and > > name Gary's tv_grab_sdjson. (no country section). If we do want a > > country code I like tv_grab_zz_sdjson.. I think keeping two letters > > looks better. :) > I think having one named tv_grab_sd_json and the other tv_grab_sdjson would be confusing as they are too similar with no obvious indication of what (if anything) is different about them. I recall you consider 'sdjson' to be the name of the data source, so I > therefore propose: > > Kevin's : tv_grab_zz_sdjson > Gary's : tv_grab_zz_sdjson_sqlite > While in the short term renaming the currently included grabber may be confusing I think long term the above suggestion is the best proposal so far. Is there any precedent for renaming a grabber? I seem to recall some code in the XMTV libraries for migrating old configuration files so I would guess yes. Could a symlink be included in some number of upcoming releases? Kevin ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ xmltv-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xmltv-devel