TTL minutes or seconds

[Sanmarcos]

The RSS 2 spec states that the <ttl> value is in *minutes*, not
seconds. See http://cyber.law.harvard.edu/rss/rss.html#ltttlgtSubelementOfLtchannelgt

However, the rssdler docs say:

scanMins: [Optional] An integer option. Default 15. Values are in
minutes.
The number of minutes between scans.
If a feed uses the <ttl> tag, it will be respected.
If you have scanMins set to 10 and the site sets <ttl>900</
ttl>
(900 seconds; 15 mins); then the feed will be scanned every
other time.
More formally, the effective scan time for each thread is:
for X = global scanMins, Y = ttl: min{nX | nX >= Y ; n ∈ ℕ}

How can this discrepancy exist?. I am currently fetching a feed (which
claims RSS 0.91) that sets TTL to "10" (Obviously, minutes).

However, with scanMins set at 11 (bigger than the TTL on the feed), I
still get this warning:

20090314.08:05 INFO RSS feed "my_feed" has indicated that we should
wait greater than the scan time you have set in your configuration.
Will try again at next configured scantime

Any insight into this matter is appreciated.

[lostnihilist]

On Saturday 14 March 2009, Sanmarcos wrote:
> The RSS 2 spec states that the <ttl> value is in *minutes*, not
> seconds. See
> http://cyber.law.harvard.edu/rss/rss.html#ltttlgtSubelementOfLtchannelgt
>
> However, the rssdler docs say:
>
> scanMins: [Optional] An integer option. Default 15. Values are in
> minutes.
> The number of minutes between scans.
> If a feed uses the <ttl> tag, it will be respected.
> If you have scanMins set to 10 and the site sets <ttl>900</
> ttl>
> (900 seconds; 15 mins); then the feed will be scanned every
> other time.
> More formally, the effective scan time for each thread is:
> for X = global scanMins, Y = ttl: min{nX | nX >= Y ; n ∈ ℕ}
>
> How can this discrepancy exist?. I am currently fetching a feed (which
> claims RSS 0.91) that sets TTL to "10" (Obviously, minutes).
>
> However, with scanMins set at 11 (bigger than the TTL on the feed), I
> still get this warning:

I will look to make sure that everything is cast to the right value, but I'm
pretty sure the code uses minutes for convenience and then multiplies by 60
to get seconds.

I do not see this behavior with similar settings.

--
lostnihilist

[Sanmarcos]

It is weird, because with the RSS feed with a ttl of 10, and scanMins
at 11 I still get the warning.

Does rssdler assume that the RSS ttl or scanMins is in seconds?

I can't seem to figure out a way to fix this.