> > I knew that if you set a cookie and then cflocate in the > > same page the cookie isn't set. I realize that client > > variables could be affected if their default storage was > > cookie, however if I was using an DB for the variable > > storage I would suspect otherwise. My theory is incorrect > > for some reason and Client variables using a DB can not be > > set with a cflocate on the same page. Is this the common > > behavior? > > Yes, this is common behavior. You see, there is no state > management on the web. There is no correlation between page > requests. The server can't tell one request from the other.
While there is no state management built into the HTTP protocol, it's incorrect to state that you can't set Client variables in a database and use CFLOCATION in the same page in most cases, even if you're using CFID and CFTOKEN cookies to associate the browser with the Client scope. Typically, when you set Client variables in a database, the CFID and CFTOKEN cookies have already been accepted. So, even if you use CFLOCATION, the browser will still subsequently send the two cookies to the page to which you've redirected (assuming that you've redirected to a page within the same site). The only time when this may not occur is on the initial page request - if you use CFLOCATION there, the browser may not receive the cookies created by the CFAPPLICATION tag. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ Get Your Own Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionb FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
