Hi,
I think the session management of the servlet-API is designed for requests
from browsers. (please correct me if this is wrong).
I've used session management with an applet-client. The problem was that
sessions could only be got by the servlet-engine, which examines cookies and
eventually encoded URLs. In the servlet-API 2.0 sessions could also be
retrieved with the session-Id from the servlet-context. But this required a
reference to an active session-object (e.g. new instantiated session) and is
deprecated since servlet-API 2.1 (security reasons).
The solution for my servlet-applet-app was that I've encoded the sessionIds
in all servlet-URLs and send those URLs with the first response to the
client. (perhaps you can do it similar in your app)
I'm still missing the feature of the servlet-API to get a session, if I know
its ID. (without detour of instantiating an other session or similar).
greets, peter
-----Urspr�ngliche Nachricht-----
Von: Mukesh Garg <[EMAIL PROTECTED]>
An: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Datum: Montag, 21. Februar 2000 08:24
Betreff: Session Maintainence
Hi
I have read lot of material on maintaining session in Servlets
but that describes only the scenario in which requests come through a
Web Browser.
What if HTTP request comes through a simple client like a Application.
or what if HTTP request is made by a Mobile phone through WAP gateway
using
WAP/HTTP protocol.
if anybody has any idea please help me
Thanx
Mukesh garg
___________________________________________________________________________
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
