Matt,

  You didn't include any code, so all I can offer is that you can use the
response.encodeURL(URL) method to enable URL re-writing.  It's nice
actually, if the browser allows cookies it will uses them for session
tracking, otherwise it will rewrite the URL.

Steve

-----Original Message-----
From: A mailing list for discussion about Sun Microsystem's Java Servlet
API Technology. [mailto:[EMAIL PROTECTED]]On Behalf Of Matt
Folkard
Sent: Wednesday, February 09, 2000 8:15 AM
To: [EMAIL PROTECTED]
Subject: Session tracking


I'm having some problems with session tracking in my servlet i.e. I can't
rewrite the URL. The servlet is going to serve WML content for WAP enabled
mobile phones so I can't rely on cookies as the browsers I'm targetting will
(mostly) not have cookie support.

The servlets run fine, and create new sessions OK, but the server will not
keep sessions alive longer than the servlet service() method lasts... I need
to know whether this a server problem (i.e. I need to enable URL rewriting)
or I'm doing something dodgy in my code...

I'm running Tomcat v.3.0 (servlet API 2.2 I think) on NT4.0 sp5

Cheers for any help

matt

___________________________________________________________________________
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

Reply via email to