Application Walkthrough
Before we jump into the actual code, let's review a frequently-used concept (and tag) in this example—cache-control. Because we are dealing with a schedule application, the back-end data will be constantly changing. Depending on how you interface to the database, it is possible that the WAP device and a static computer terminal could be interacting with the data simultaneously. Therefore, it is important that we keep track of the WAP device's cache- management.
Caution
If we let the WAP device control the cache itself, the browser could choose to use cached pages as opposed to loading modified pages. As a result, the schedule may appear static.
Because the header and this initial code will be consistent throughout ...
Get WAP Development with WML and WMLScript now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
