Feeds not updated for about a week

104 views
Skip to first unread message

Tamotsu TAKAHASHI

unread,
Jul 29, 2014, 6:45:39 AM7/29/14
to google-ajax...@googlegroups.com
Has Feed-API been stopped, or am I just too impatient? I don't see any updates on my feeds for a number of days.
The feeds (fullrss.net) are updated in fact if I access the feeds directly. So it seems that Google servers are returning their old cached data.
I've used the API (and haven't changed the script) for months. Until July 20th, I hadn't seen such a long delay. (IIRC the longest was a day or less)

Jeremy Geerdes

unread,
Jul 30, 2014, 4:31:44 PM7/30/14
to google-ajax...@googlegroups.com
There has been no announcement of deprecation - much less discontinuation - for the Google Feed API that I've seen. However, it should be noted that the Feed API's TOS explicitly state that the deprecation policy (which says Google will give three years' notice before discontinuing the service) will no longer be applicable from April 20, 2015. (I.e., the service may be discontinued at any time, with or without warning, after that date.)

That said, feeds have always been cached, so there has always been a delay between an update of the live feed and such updates appearing via the Feed API. If you would like to ensure the freshest available content, the quickest and easiest workaround is to add a cache-busting parameter to the end of your feed URL, as in the JS example below:

var url = 'http://www.mysite.com/path/to/my/feed.rss?nocache=' + (new Date).getTime();

This will almost ensure a unique feed url every time you request the feed, and so the API's backend will go crawl the feed as though it was new.

Of course, this could also introduce the possibility - particularly if your server is slow in returning the feed - that the API times out and returns an error about being unable to fetch the feed. So you'll want to make sure you have logic to handle that and send the same request a second time if necessary.

jg



--
--
You received this message because you are subscribed to the Google
Groups "Google AJAX APIs" group.
To post to this group, send email to
google-ajax...@googlegroups.com
To unsubscribe from this group, send email to
google-ajax-searc...@googlegroups.com
To view this message on the web, visit
https://groups.google.com/d/msgid/google-ajax-search-api/152d4fbc-15c4-4ad4-8e93-5374063a3429%40googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-ajax-searc...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Jeremy R. Geerdes
Generally Cool Guy
Des Moines, IA

If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan Church!

Tamotsu TAKAHASHI

unread,
Jul 31, 2014, 4:33:54 AM7/31/14
to google-ajax...@googlegroups.com
Hi Jeremy,


There has been no announcement of deprecation - much less discontinuation - for the Google Feed API that I've seen. However, it should be noted that the Feed API's TOS explicitly state that the deprecation policy (which says Google will give three years' notice before discontinuing the service) will no longer be applicable from April 20, 2015. (I.e., the service may be discontinued at any time, with or without warning, after that date.)

I didn't know that. Thanks for the information!
 
That said, feeds have always been cached, so there has always been a delay between an update of the live feed and such updates appearing via the Feed API. If you would like to ensure the freshest available content, the quickest and easiest workaround is to add a cache-busting parameter to the end of your feed URL, as in the JS example below:

var url = 'http://www.mysite.com/path/to/my/feed.rss?nocache=' + (new Date).getTime();

This will almost ensure a unique feed url every time you request the feed, and so the API's backend will go crawl the feed as though it was new.

Of course, this could also introduce the possibility - particularly if your server is slow in returning the feed - that the API times out and returns an error about being unable to fetch the feed. So you'll want to make sure you have logic to handle that and send the same request a second time if necessary.

Yes, unfortunately it seems that your trick always times out for my feeds.
Anyways, your advice is really helpful. Thanks a lot!

Regards,
-- 
tamo



On Tue, Jul 29, 2014 at 5:45 AM, Tamotsu TAKAHASHI <tta...@gmail.com> wrote:
Has Feed-API been stopped, or am I just too impatient? I don't see any updates on my feeds for a number of days.
The feeds (fullrss.net) are updated in fact if I access the feeds directly. So it seems that Google servers are returning their old cached data.
I've used the API (and haven't changed the script) for months. Until July 20th, I hadn't seen such a long delay. (IIRC the longest was a day or less)

--
--
You received this message because you are subscribed to the Google
Groups "Google AJAX APIs" group.
To post to this group, send email to
google-ajax...@googlegroups.com
To unsubscribe from this group, send email to

To view this message on the web, visit
https://groups.google.com/d/msgid/google-ajax-search-api/152d4fbc-15c4-4ad4-8e93-5374063a3429%40googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-ajax-search-api?hl=en?hl=en

---
You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-ajax-search-api+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages