How HDML services can use notifications

The previous sections described the different notification content types and delivery channels. The following table lists some common applications for notifications and some recommendations on how to implement them.

Application	Recommended Channel	Recommended Content Types	Description
Inform the subscriber of timely and volatile information (such as changes in stock prices)	Push	Alert and Cache Operation (optional)	The service sends a push notification containing an alert. The alert specifies a URL which provides the latest stock price. If the alert URL might be already by cached in the UP.Phone, you should include a Cache Operation in the notification to invalidate it.
Ensure that obsolete information (such as a changed directory entry) is removed from the UP.Phone cache	Push	Cache Operation	The service sends a push notification containing a cache operation, which removes the specified URL from the cache. The next time the user navigates to the URL, the UP.Phone requests it from the UP.Link server, ensuring that the URL is up-to-date.
Update timely but nonvolatile information, such as sports scores, without interrupting the subscriber.	Pull	Cache Operation and HDML deck	The service sends a pull notification containing an HDML deck and a cache operation (to ensure that the old version of the deck is removed from the cache). The next time the user navigates to the deck, it will already be updated so the user won't need to request it again.

Application

Recommended Channel

Recommended Content Types

Description

Inform the subscriber of timely and volatile information (such as changes in stock prices)

Push

Alert and

Cache Operation (optional)

The service sends a push notification containing an alert. The alert specifies a URL which provides the latest stock price.

If the alert URL might be already by cached in the UP.Phone, you should include a Cache Operation in the notification to invalidate it.

Ensure that obsolete information (such as a changed directory entry) is removed from the UP.Phone cache

Push

Cache Operation

The service sends a push notification containing a cache operation, which removes the specified URL from the cache. The next time the user navigates to the URL, the UP.Phone requests it from the UP.Link server, ensuring that the URL is up-to-date.

Update timely but nonvolatile information, such as sports scores, without interrupting the subscriber.

Pull

Cache Operation and HDML deck

The service sends a pull notification containing an HDML deck and a cache operation (to ensure that the old version of the deck is removed from the cache).

The next time the user navigates to the deck, it will already be updated so the user won't need to request it again.

Of course, these are just a few recommendations. Depending on your needs, there is a variety of permutations of content types and delivery channels you can use.