I second that book recommendation, I think every Java web developer should have in on their desk. At times it can be a little TOO light-hearted, but it never fails to get the pertinent information across in a very understandable way. Probably shouldn't be the ONLY book on ones' desk, but it is very good.
-- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com On Wed, August 3, 2005 3:18 am, Bernhard Slominski said: > Well, nobody likes to go through the specs, an excellent book which covers > the session handling very well to is: > "Head First Servlets and JSP" > http://www.amazon.com/exec/obidos/tg/detail/-/0596005407/qid=1123053380/sr=8 > -1/ref=pd_bbs_sbs_1/103-1556156-2935038?v=glance&s=books&n=507846 > > Bernhard > > >> -----Ursprüngliche Nachricht----- >> Von: Charles P. Killmer [mailto:[EMAIL PROTECTED] >> Gesendet: Dienstag, 2. August 2005 19:08 >> An: Tomcat Users List >> Betreff: RE: Session ID's >> >> >> Thanks. I will take a look through this. >> >> Charles >> >> -----Original Message----- >> From: Bernhard Slominski [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, August 02, 2005 10:33 AM >> To: 'Tomcat Users List' >> Subject: AW: Session ID's >> >> Some small addition: >> URL Rewriting is only used when cookies are switched off. >> >From the Servlet Spec: >> >> SRV.7.1.3 URL Rewriting >> URL rewriting is the lowest common denominator of session >> tracking. When a client will not accept a cookie, URL >> rewriting may be used by the server as the basis for session >> tracking. URL rewriting involves adding data, a session ID, >> to the URL path that is interpreted by the container to >> associate the request with a session. >> The session ID must be encoded as a path parameter in the URL >> string. The name of the parameter must be jsessionid. Here is >> an example of a URL containing encoded path information: >> http://www.myserver.com/catalog/index.html;jsessionid=1234 >> >> SRV.7.1.4 Session Integrity >> Web containers must be able to support the HTTP session while >> servicing HTTP requests from clients that do not support the >> use of cookies. To fulfill this requirement, Web containers >> commonly support the URL rewriting mechanism. >> >> Bernhard >> >> > -----Ursprüngliche Nachricht----- >> > Von: Charles P. Killmer [mailto:[EMAIL PROTECTED] >> > Gesendet: Dienstag, 2. August 2005 17:03 >> > An: Tomcat Users List >> > Betreff: RE: Session ID's >> > >> > >> > I was hoping there was a configuration setting that would tack the >> > session id onto every hyperlink at runtime, much as PHP does. >> > >> > Charles >> > >> > -----Original Message----- >> > From: Derrick Koes [mailto:[EMAIL PROTECTED] >> > Sent: Tuesday, August 02, 2005 9:20 AM >> > To: Tomcat Users List >> > Subject: RE: Session ID's >> > >> > Use HttpServletResponse.encodeURL(String url) >> > >> > -----Original Message----- >> > From: Charles P. Killmer [mailto:[EMAIL PROTECTED] >> > Sent: Tuesday, August 02, 2005 10:04 AM >> > To: Tomcat Users List >> > Subject: Session ID's >> > >> > Is there a configuration setting such that every local URL will be >> > encoded with a session id if one is present? I have >> developed a site >> > that uses cookies to hold the session id and am getting complaints >> > from users that do not have cookies enabled. >> > >> > Thanks >> > Charles >> > >> > >> --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
