The meta Pragma

The meta pragma allows arbitrary meta-information to be included in a WML deck. There are three variations on it:

use meta name name value scheme;
use meta http equiv name value scheme;
use meta user agent name value scheme;

In all cases, the three parameters name , value , and scheme are all normal WMLScript string literals. The name parameter specifies a property name, and value specifies its value. The scheme parameter is optional: it specifies how the property is to be interpreted. It’s not used by anything defined in the official standards but might be used in some implementation-specific way.

The interpretation of the meta-information depends on the form used:

meta name

Meta-information specified with this form is for the origin server’s use only. It isn’t transmitted to the client. For example:

use meta name "last-modified" "2000-05-15";
meta http equiv

Specifies an HTTP or WSP header to be sent along with this WMLScript file. This can specify how the file should be cached and many other things. For example:

use meta http equiv "cache-control" "no-cache";
meta user agent

Specifies a property that is passed to the WMLScript interpreter. It’s up to the browser to decide what to do with it. No specific property names are officially defined. If a particular browser supports such information, you need to consult its documentation to find the names of the properties and what their values should be. For example:

use meta user agent "x-debugging" "on";

Get Learning 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.