For latency reasons, feeds and gadget XML files are cached by Google for a few hours. This has a number of implications for developers.
- When developing a gadget, changes to the XML will not be immediately visible by default. It's recommended that you add the "My gadgets" gadget, which allows you to disable caching on a per-gadget-instance basis as a workaround. This will not disable caching for all instances of your gadget, just the instance on your iGoogle page.
- As a result of the above, when pushing changes to your gadget into production, you'll want to ensure that the cached version of your gadget will continue to operate until the new version has a chance to propagate through the cache. For instance, if you reference feed_url_1 in the old version of your gadget, and feed_url_2 in the new version of your gadget, make sure that you continue to serve feed_url_1 until all of your users are on the new version of the gadget.
CSS, JavaScript, and images included in your gadget are not automatically cached by iGoogle unless you explicitly use the iGoogle proxy. If any of these files fail to update when you modify them, it's likely the cause of the browser. Clearing your cache should correct the issue.
|
|