> > > > You could just make sure that if the user clears the check
> > > > box, their cookies don't persist after they close their browser,
> > > > by overwriting the cookies with non-persistent cookies...
> ...
> > > Question, won't this get a bit screwy in a clustered enviroment?
>
> > No, it shouldn't, if you're using a common data repository
> > for the client variables. No matter which cluster member you
> > connect to, it's going to use those cookies to look up your
> > client variables from the database. The only thing that
> > overwriting the cookies does is makes them disappear after the
> > user closes the browser.
...
> I lost Dave's first reply, so he may have covered this, but
> in a clustered environment you'll want to set up the cookie
> so that it will be sent to all machines in the cluster.
>
> <Cfcookie name="CFID" value="#CFID#" domain=".mycompany.com">
>
> by using domain=".mycompany.com" you ensure that the cookie
> will be sent to www1.mycompany.com, www2.mycompany.com, etc.
> If you don't specify domain, the cookie will only be sent to
> the origin machine, so you would see funny behavior in a
> clustered environment - each server would set its own cookies
> and have its own client variables.
I think I may have neglected to mention that. In addition, with CF 4.5.x,
there'll be a third cookie if you're using the SETDOMAINCOOKIES attribute of
CFAPPLICATION; this cookie, called CFMAGIC, is an indicator to CF that it's
using domain cookies rather than host cookies to track information. You'd
want to overwrite CFMAGIC the same way, specifying the DOMAIN attribute for
that one as well.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
