Re: [xmltv-users] UK Atlas load/usage warning email

Nick Morrott <[email protected]>
Newsgroups gmane.comp.tv.xmltv.devel
Message-ID <CAOQWjw0C0dhxoMx0MA+Gfp8a_Y4F3KYDp0gdSiRGxM8EoA-tdg@mail.gmail.com>
On 12 May 2016 at 13:46,  <[email protected]> wrote:
> On Thu, 12 May 2016 09:26:01 +0100, Ian Campbell wrote:
>
>> On Thu, 2016-05-12 at 09:01 +0100, [email protected] wrote:
>> > The grabber will fetch a 'calendar' day - i.e. one in GMT. So
>> > fetching today will actually fetch from 23:00 yesterday to 23:00
>> > today. I suspect mythfilldatabase then drops the hour that is
>> > 'yesterday' so you think it is fetching 00:00-23:00.
>>
>> I just misread the grabber code, I don't think myth will drop anything
>> (except perhaps things actually in the past). In any case I think it is
>> working as intended, i.e. fetching N days worth in 24hr increments
>> (whichever 24hr span it happens to be, it'll line up into a continuous
>> span), is that right?
>>
>> Ian.
>
> I'm not sure what you are asking. tv_grab_uk_atlas will fetch whatever timespan you ask for, as a single pull.  (I don't know what mythfilldatabase does as I don't use it.)
>
> The suggestion from Robert for the grabber to fetch and concatenate a fetch in 24 hour 'blocks' is only a proposal at this stage.

In the general case:

i) if an upstream data source's API specifies as part of its terms and
conditions of use that no consuming application request more than 24
hours of data in a single API call; and

ii) a consuming application is asked to fetch n days of listings (n > 1); and

iii) said application makes a single API call, requesting the n days
of data in a single call, rather than 5 separate requests (day n, day
n+1, day n+2,...) the consuming application is not compliant with the
upstream Terms.

It does not matter if an application provides additional options that
*could* be used to request the data in accordance with the Terms and
Conditions. It does not matter if a developer does not agree with the
Terms of use.

If it is possible for an application to breach the Terms of its
upstream data source during normal use it needs to be updated to
ensure all possible use cases respect upstream's Terms of use.

Additionally, if Terms of use for a data source change over time, it
is a developer's responsibility to ensure the consuming application
stays compliant.

Thanks,
Nick

------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
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.