Session handling
Some WAP gateways support cookies, so we can rely on them to keep the session id on behalf of the phone
Some WAP gateways send the subscriber ID as a header with each request; we can make use of this id as the session identifier
Many WAP gateways do not support cookies: we can set a variable on the phone that’s presented with each request, it will act as the session id
When everything else fails, we can use URL rewriting; this however increases the size of the pages and makes them non-cacheable
Notes:
If the session handling is done by using a WML variable on the cell phone’s browser, that variable has to be presented in all the further requests made to the Web server. This is taken care automatically by the XSLT stylesheets if the developer uses the XHTML language part of our framework.