Hello J Miguel
If you try the above method successfully, please let me know and send the
code to obtain the identifier from the gateway.
Thank you very much
Un saludo
-----Mensaje original-----
De: A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED]]En nombre de Jes�s
Gabriel y Gal�n
Enviado el: mi�rcoles, 29 de agosto de 2001 10:12
Para: [EMAIL PROTECTED]
Asunto: Re: wap wml and sessions
From: "Alberto Imedio" <[EMAIL PROTECTED]>
> Hi All,
>
> I've experience in PDA development. In PDAs, each dispositive is capable
to
> send its identifier, unique in each machine, and this is the better way to
> maintain the sessions. Do you know if wap devices send any identifier in
> each request?
I assume that the servlets that receive the request are being invoked by a
WAP Gateway directly. The WAP Gateways always (well not _really_ always)
identify de originator of the request and assigns them a unique identifier
within the gateway. You can configure the gateway to pass that information
in the http headers. In that way you can have a unique user identifier that
can be used to obtain the session. Although I haven't done it with servlets
I suppose it won't be very difficult, provided that you have a unique way of
identifying a client within the request.
Jesus Gabriel y Galan.
> De: A mailing list for discussion about Sun Microsystem's Java Servlet
>
> Hello all,
>
> I'm working on wml generation from servlets and I'm having trouble to
> maintain sessions between calls. And our
> development library is heavily session based..
>
> As far as wap devices do not usually support cookies, what aproach should
I
> take?. I suppose I shouldn't use url
> rewritting as I'm using the post method. Do I need to do it as postfield?.
> Any experience anyone?
>
> Thank you.
>
>
>
> --
>
>
> saludos,
> jmiguel
>
> Virtual Software,
> http://www.virtualsw.es/
> ICQ 13550064
>
>
___________________________________________________________________________
> 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
>
>
___________________________________________________________________________
> 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
>
>
___________________________________________________________________________
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
___________________________________________________________________________
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
