The HttpSession does what you say, associates a 'session' (some java object)
with an id. The id is passed as the Cookie to the browser.
And yes URL re-writing does entail changing all of the URLs on a page
dynamically so that each client sees a unique URL - you don't need to use
JavaScript, you encode the URLs in the JSP page using a scriptlet (or
equivalent),
Kevin Jones
DevelopMentor
-----Original Message-----
From: A mailing list about Java Server Pages specification and reference
[mailto:[EMAIL PROTECTED]]On Behalf Of Duffey Kevin
Sent: 17 January 2000 23:47
To: [EMAIL PROTECTED]
Subject: Session tracking?
Hi all,
I am stuck on one thing. I know JSP turns into servlets and all, and
session tracking is easy with HttpSession. What I am confused about is, can
I keep each individual client in a session throughout the site without
using cookies OR url rewriting? Will the HttpSession do this for me? Or
MUST I use some way of passing the session ID around? It appears we use
cookies right now, but are considering URL Rewriting because some of our
clients are behind firewalls and their IT guys wont allow cookies to pass.
What does URL Rewriting entail anyways? Do I really have to turn EVERY
SINGLE LINK into some special javascript call or somehow pass the session
ID on every single link? We have about 1200 links on our site, and I would
hate to think that I have to add something to every single one of them.
Thanks.
Kevin Duffey
Software Engineer
[EMAIL PROTECTED]
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff
JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
