If you are setting up a cache to handle the requests for cells, it is possible that your users will be looking at stale content. This may be a problem with user-generated content, where editors expect their changes to be visible immediately.

The client application will, if instructed, handle cached content. When a user loads a page with potentially stale content, the client will request the latest content from our server -- if the version served on your page is not the most recent, it will replace the cell content on the page with the new content.

To inform us about caching call the client application's WPCAPI.setCachedContentHandling() method and pass true as the parameter.

Example

WPCAPI.setCachedContentHandling(true);

Delayed Rendering

Because the content may be different between versions, we hide the original content on the page until we've verified the version. This prevents a "shifting" from occurring; it would be distracting to see the content change automatically. However, this does delay the rendering of the content until later in the pageload process. Only set the client-side parameter if you are indeed caching your requests to avoid doing this unnecessarily.

Next Step 10: Subscribe To The Data Feeds