The problem I found with the bustcache params is Google has their timeout set ridiculously fast and I very very often got an error as it would time out before it gave the page/site a chance to respond.
This lead to the Feed API v2 with Push and PubSubHubBub but that got discoed so we are back to square one with this issue. I ended up just making my own feedfetcher where I can control the cache time myself. Alternatively, if it's something like a Blogger feed then I use that API instead, well not really an API per se' you can request the feed in JSONP format then just parse it that way. On Mar 22, 1:19 pm, Jeremy Geerdes <[email protected]> wrote: > Sorry, I should have been more clear. I meant that you should add a > cache-busting parameter to your feed url. For instance, if your feed url > ishttp://www.mydomain.com/my/feed/url.atom, change it > tohttp://www.mydomain.com/my/feed/url.atom?cachebuster=some_random_string > > Jeremy R. Geerdes > Generally Cool Guy > Des Moines, IA > > For more information or a project quote: > [email protected] > > If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan > Church! > > On Mar 22, 2011, at 2:17 PM, Benjamin wrote: > > > Thanks for the replies. Yes, the lag is what I am talking about. > > acting on your first suggestion, I have added cache-busting param in > > the head: <META HTTP-EQUIV="Pragma" CONTENT="no-cache"> but i don't > > know if it will do the trick. > > > On Mar 22, 2:11 pm, Jeremy Geerdes <[email protected]> wrote: > >> If you're talking about the lag between the time that you post a new entry > >> to your RSS and it's actually displayed in a Feeds API-based application > >> (e.g., the Dynamic Feed Control), then this is normal. Google servers > >> cache your feed the first time you access it and then refresh the cache > >> only every so often so as to improve performance and save your server the > >> potential strain. The documentation used to say that this refresh would > >> generally come no more than once every 60 minutes, but that it would vary > >> depending on the popularity of your feed. There is no known way to work > >> around this. > > >> Jeremy R. Geerdes > >> Generally Cool Guy > >> Des Moines, IA > > >> For more information or a project quote: > >> [email protected] > > >> If you're in the Des Moines, IA, area, check out Debra Heights Wesleyan > >> Church! > > >> On Mar 22, 2011, at 12:51 PM, Benjamin wrote: > > >>> When RSS feed is displayed using Google API, the contents of the > >>> original RSS feeds are not instantaneously displayed in Dynamic Feed > >>> Control - Vertical (http://code.google.com/apis/ajax/playground/ > >>> #dynamic_feed_control_-_vertical); the lapse is sometimes more than 30 > >>> minutes. Wonder if there is any way to speed this up by manipulating > >>> the code? > > >>> -- > >>> You received this message because you are subscribed to the Google Groups > >>> "Google AJAX APIs" group. > >>> To post to this group, send email to > >>> [email protected]. > >>> To unsubscribe from this group, send email to > >>> [email protected]. > >>> For more options, visit this group > >>> athttp://groups.google.com/group/google-ajax-search-api?hl=en. > > > -- > > You received this message because you are subscribed to the Google Groups > > "Google AJAX APIs" group. > > To post to this group, send email to > > [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group > > athttp://groups.google.com/group/google-ajax-search-api?hl=en. -- You received this message because you are subscribed to the Google Groups "Google AJAX APIs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-ajax-search-api?hl=en.
