It looks like the path to weblogs.com/changes.xml is kaput (for now, please post if you have any other news) Dave is also throttling down users who abuse the service. Here is a quote from his blog which is important to consider when setting up your cahce time.
Throttling down, part 2Here’s how I’m handling apps that request changes.xml too often. The rule is that you may access changes.xml three times an hour. After that you’ll get a 503 Service Unavailable response. I also included a Retry-After response header.
- You must be logged in to reply to this topic.