On 21 May 2016 at 07:22, Robert Eden <[email protected]> wrote:
[...]
> What do folks think is a proper name for a SD-JSON grabber since it covers
> so many countries?
On Mon, 23 May 2016 03:17:28 +0100, Nick Morrott wrote:
> I don't think we should include "json" in a new grabber's name unless
> it would otherwise conflict with an existing grabber of the same
> prefix name (e.g. if there was already a tv_grab_sd grabber) that uses
> a different data service API.
I agree. I think it's wrong to include the retrieval method in the name. Otherwise they should be called _dk_www, _br_www, _is_xml, _uk_rt_csv, _uk_atlas_json, etc. Factually accurate, but unnecessary.
On Sun, 22 May 2016 22:27:34 -0500, Robert Eden wrote:
> If you look at most of the other grabbers, the last part of the name is
> a source description. SD-JSON is
> the name of the data source, that's why I proposed it end in SDJSON, not
> just JSON.
> JSON (without the SD) is the name of a data transfer syntax and I agree
> not appropriate.
I think that's only the case to distinguish between 2 or more grabbers for the same country (e.g. _uk_rt, _uk_atlas, _uk_tvguide), but here the final element represents the 'source' and not the 'method'. So for the SD grabber this should be 'sd' (source) not 'json' (method). Otherwise it should be tv_grab_uk_atlas_json etc. which is getting daft.
On Mon, 23 May 2016 08:38:35 +0200, Karl Dietz wrote:
>
> this grabber has a reversed naming scheme... The dtv in _dtv_la is the
> data source, the service area is _la :-)
> "Latin America Direct TV listings"
Yes that grabber is clearly wrongly named and should be _la_dtv
On Mon, 23 May 2016 10:45:36 +0100, Ian Campbell wrote:
>
> With tab completion and the current set of grabbers today it's actually
> just:
> 'g' <TAB>
> which is two characters ;-)
Not in Windoze it's not ;-)
On Mon, 23 May 2016 17:32:17 +0200, Hika van den Hoven wrote:
>
> Have you even thought about the distinction between country and
> language ;-)
I believe the grabber name should relate to the 'source' and not the 'language'. A number of the grabbers allow language selection; this is done as part of the configuration. e.g. There is not a separate grabber for _dtv_la_es and _dtv_la_pt_br (since they both use the same 'source' data).
On Mon, 23 May 2016 07:07:55 +0100, John Veness wrote:
>
> I quite like "global". It rolls off the tongue better than "zz".
I think 'global' should only be considered where a grabber is truly global, which, of course, none are. Otherwise it's just misleading, e.g. "yes it's global, but only covers USA, Canada, UK, Germany". Misleading IMO.
How about: tv_grab_xx_sd_file and tv_grab_xx_sd_sqlite to reflect the different caching methods (and prerequisites).
Geoff
------------------------------------------------------------------------------
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. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.