right, but if you restart your browser, session will be invalidated, as coockie is (by default) set to a browser instance.
The way coockies are stored on windows (NT) platform has no impact on session tracking mechanism. Nico. > but however if one uses the cookies for saving the sessionId on the > customer, > the cookie is saved under a "user" directory > C:\WINNT\Profiles\<user-name>\Cookies. > the <user-name> reprensents a physical person for cookie information, isn't > it ? > > > > ----------------------------------------------------------- > As of February 12, 2003 Thomson unifies its email addresses on a worldwide > basis.Please note my new email address: [EMAIL PROTECTED] > > Thomson is the leader in solutions and technologies for the entertainment > and media industries and serves its customers under its four strategic > brands: Technicolor, Grass Valley, RCA and THOMSON. > More about Thomson: http://www.thomson.net/videochain > > ----Original Message----- > From: Nicolas De Loof [mailto:[EMAIL PROTECTED] > Sent: 06 March 2003 10:32 > To: Struts Users Mailing List > Subject: Re: Association between Session object and Cookies/URL > rewriting > > > > I well understand now that Sessions (object on the web server) are > > used either cookies or URL writing (in the client side). > > In the struts application I have to make changes if I want to > > use URL rewriting. > > But what I still do not understand (I am sorry to be also insistent) > is > > why/or how each user will have a own unique sessionID ?. > > How a user is identified? > > What distinguish a client from an other client ? > > Is the user NT account ? > > Perhaps a client is not a "physical" person but an instance of Web > browser , > > > > A "client" is not a "physical" person but an instance of a browser : > When J2EE server doesn't get any session info from request (form > coockie or request parameter if url rewriting is used), it will > generate a new session id for "client". Every new request from this > browser will come with sessionid, and a pseudo-connection will be > maintained between browser and server. > > A "user" is indentified by the browser instance it is using. > > Nico. > > > -------------------------------------------------------------------- - > 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]
