You don't necessarily have to use a database if that's a problem for where you're hosted. You could just dump copies of the feeds to file and check on their last modified time to determine whether to fetch a new one or not.
Regardless of whether the amount of requests would be acceptable, you don't really want to be doing external web requests at the same time as someone requests one of your pages because that means your site can only be as quick as the round trip from your server to fetch data from the BBC and back again. Ideally this would be happening in the background via a cron job (if you have that facility). On Feb 11, 2008 10:03 AM, Rob Dunfey <[EMAIL PROTECTED]> wrote: > Thanks for all the replies. > > I had hoped to avoid collating the feeds in my own database, as the database > would have to be maintained by tech services. I will proceed as initially > planned without any database, but change the application to make > significantly less queries to be on the safe side. > > At some point in the future, perhaps the BBC could look into providing > collated weather feeds for each of the continents, e.g. one feed for all > European capitals, one feeds for all North American capitals? It would be > the same data but just 5 requests, instead of the hundreds currently > required. > > All the best and many thanks, > > Rob - Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html. Unofficial list archive: http://www.mail-archive.com/[email protected]/
