Dan Muey wrote:
> > -----Original Message-----
> > From: Randal L. Schwartz [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, September 04, 2003 12:33 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Test if browser's allows cookies/has them turned onetc..
> >
> >
> > >>>>> "Dan" == Dan Muey <[EMAIL PROTECTED]> writes:
> >
> > Dan> As much as I hate to do stuff that requires cookies, there is a
> > Dan> project I'm doing that requires cookies.
> >
> > This should have been on [EMAIL PROTECTED] instead.
> > More experts there about this stuff.
> >
> > Having said that, you should read my "basic cookie
> > management" column at
> > <http://www.stonehenge.com/merlyn/WebTechniques/col61.html>.
>
> > I'm told that code was made into a module, but I can't seem to find that reference
> > now.
>
> Cool, that's pretty much the method I was using so I guess I'm not crazy!
> I agree with your sentiments about cookies in the article. I try to avoid
> them when ever possible but this one app will require them, either that or
> I have to make sure the data is passed in every invokation of the script
> via link or form which might just be worth the trouble.
YES!! It definitely is worth the trouble, and it is not that much trouble, if your
routing
is well-designed. I haven't used the CGI module much, but I can tell you that
<input type="hidden" name="info_tag" value="whatever is currently useful for this
stage">
works quite well, and should be returned as $cgi_object->param{'nfo_tag'}.
Much better than playing with your audience's file system.
Joseph
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
