Finally, the personalized weather page would not be cached at all—at least, not on your M-Business Sync Server. This might seem strange, given that your weather reports probably do not change more than once a day. But if you are creating personalized content, the page is going to change from person to person, so the cached version on the M-Business Sync Server is essentially useless. After all, you do not want to be accidentally giving somebody in Minneapolis the weather report for Phoenix.

You do want the personalized weather page to be cached on users' mobile devices. For more information, see Caching personalized content on user's device.

Now that you understand caching strategies, the next section looks at how to implement caching on an M-Business channel.