>>> Mark Galbreath <[EMAIL PROTECTED]> 10-May-01 1:00:46 AM >>>
>Strictly speaking, cookies are not part of the
>WAP 1.1 specification, and it is currently very
>rare for a WAP device to support them. However,
>many gateways (most notably the UP.Link, which
>is what I use) can store cookies on behalf of devices.
>The main reason for the cookies not to exist on a WAP
>device is that they are costly (in terms of processing
>power and memory) to implement.
>One possible alternative is to implement the hidden
>field functionality of HTML.
In the past I've used HTTP authentication as a means of creating some
session semantics. Authenticated users have usernames (and realm names
and passwords) which allows you to store information in a hash that
you can reproduce whenever the authenticated person turns up.
Because you know when you get new authentications you can control the
session environment to a certain extent (ie: you can ensure that only
one person at a time has the session).
Does WAP have an authentication scheme? If so it could be used in a
similar way.
Nic Ferrier
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
