This week's book giveaway is in the Android forum.
We're giving away four copies of Head First Android and have Dawn & David Griffiths on-line!
See this thread for details.
The moose likes Web Component Certification (SCWCD/OCPJWCD) and the fly likes Cookies issue Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Head First Android this week in the Android forum!
JavaRanch » Java Forums » Certification » Web Component Certification (SCWCD/OCPJWCD)
Bookmark "Cookies issue" Watch "Cookies issue" New topic
Author

Cookies issue

Nishant Dhar
Greenhorn

Joined: Sep 09, 2005
Posts: 26
HFSJ (pg 249) says that setMaxAge(-1) means that the cookie will disappear from the client, as soon as the browser quits. what can be the argument to
setMaxAge(?), so that the cookie lives permanently on the client machine, so that it can be reused later with another request from the client.

Also on the client side(browser), the cookie is essentially a name value pair. But On the server there is a full fledged cookie object for each cookie created. is the cookie object garbage collected after the session object(which caused the cookie object to be created in case of a jsessionid cookie) is garbage collected.
Alec Lee
Ranch Hand

Joined: Jan 28, 2004
Posts: 569
As far as I know, the cookie state management mechanism does not support permanent cookie. Cookie can either be (1) invalidated immediately (2) expires after a period of time (3) deleted when browser exit. I guess the best we can do is to return a very long expiry date to mimic 'permanent'.

Please correct me if I am wrong.
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Cookies issue
 
jQuery in Action, 3rd edition