There's an option somewhere to put the session ID into the URL. You can store state information in the session. Be careful, a browser with two windows will share the session between the two windows, so that a user may get very confusing results when you store "currentpage" in the session. Typically, the session is only used to store user login credentials, but not application data/state.
You can store information on the client using "hidden" field on forms, which will send their data back when submitted. You can also add extra data in URLs, by adding parameters (e.g. href="nextpage?page=6&queryid=10") or extra 'path' information (href="nextpage/10/6"), which is very handy if you want to preserve user input across many links (any link will be relative to the URL that was used to reach this page, so "../7" could refer to page 7 of the same query). You can safely store a few kB of information in hidden fields or URLs without affecting performance. M. > -----Original Message----- > From: Peter Chen [mailto:peter.c...@aicent.com] > Sent: dinsdag 12 januari 2010 10:01 > To: users@tomcat.apache.org > Subject: if user's browser doesn't support Cookies, then > where to store user's session information? > > Hi, all > > I am using Tomcat 5.5.26 as the Web Server. I know the > session information is stored in Cookies with the key JSESSIONID. > > > > But some browsers don't support Cookies. > > So my question is if user's browser doesn't support Cookies, > then where to store user's session information? > > And besides session, how to store other user's state > information, because HTTP protocol is a stateless protocol? > > > > Thanks. > > > > This message and attachment(s) are intended solely for use by the addressee and may contain information that is privileged, confidential or otherwise exempt from disclosure under applicable law. If you are not the intended recipient or agent thereof responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone and with a 'reply' message. Thank you for your co-operation. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
