On Nov 30, 2003, at 10:50 AM, Uzo Uzo wrote:
> Well, I got it seeing my cookies, the search on the discuss is broken=20=
> as of now, so I can't search further on it.=A0 But my app is still=20
> broken.=A0 I still have more questions, when I receive a cookie, how =
do=20
> I check if it is expired?=A0 Does webware help at all? or must my app=20=
> save that information and validate the expiration of the cookie=20
> everytime?=A0 Also where is the best place to handle it, in the awake =
or=20
> respond cycle?=A0
When you receive a cookie, all you get is the text value of the cookie.=20=
You won't know when it expires, what its path is, or anything else --=20=
this information simply isn't provided by the browser. If you want=20
anything more sophisticated than simple, short text values, I'd=20
recommend using the session.
I'd generally put the cookie handling in awake(), but there's nothing=20
wrong with handling it elsewhere.
--
Ian Bicking | ianb@... | http://blog.ianbicking.org
|