CF_FormURL2Attributes is also used so you don't have be concerned with the type (url
or form) you pass a variable in.
------Original Message------
From: "Robert Everland III" <[EMAIL PROTECTED]>
To: CF-Talk <[EMAIL PROTECTED]>
Sent: November 11, 2000 5:30:31 PM GMT
Subject: RE: Maintain State Without Cookies
You're only supposed to get one cfid and cftoken per session, if you're
getting more than that per session that is why your state is not being kept.
You cant associate one session with more than one number, how is the
database going to know which variables are for which. The reason cookies are
good is because as soon as you go there the cookie is written with your own
cfid and cftoken, after that it is no longer written to. To keep the cfid
and cftoken in the url is good because it does the same thing just wouldn't
allow someone who comes back to keep the same session they had before. You
don't need CF_FormURL2Attributes to do that. That tag is only to make search
friendly urls.
Bob Everland
-----Original Message-----
From: paul smith [mailto:[EMAIL PROTECTED]]
Sent: Saturday, November 11, 2000 11:57 AM
To: CF-Talk
Cc: [EMAIL PROTECTED]
Subject: Maintain State Without Cookies
Listers: I'll try posting this again. I couldn't get CF_FORMURL2ATTRIBUTES
to work so I coded an alternative to illustrate my question. You can see
the following in action at http://www.erovera.com I'm working on
maintaining state without using cookies. This is achieved in the example
code below because each user's URL for the website is made unique by
including each user's unique CFID/CFTOKEN values in that user's URL for
each page requested. The problem is that once a CLIENT variable is set each
new page request sets a new CFID/CFTOKEN pair. This is unnecessary load on
the CVR database. Worse, the current CLIENT variables values are those
associated with the latest CFID/CFTOKEN pair, NOT the CFID/CFTOKEN pair
reflected in the URL. This makes CLIENT variables practically useless since
we would not know which CFID/CFTOKEN pair reflected the correct value of
the CLIENT variable simply by using the CFID/CFTOKEN pair in the URL. I can
work around this by setting up a new DB table to store "client" variables
associated with each CFID/CFTOKEN pair as their values are reflected in the
URL, but this is not as convenient as using ordinary CLIENT variables
stored in CDATA. Any suggestions? best, paul
========================================= ERROR!
=========================================
============================================== This is Page1.cfm Click
here to go to Page2.cfm
============================================== This is Page2.cfm Click
here to go to Page1.cfm #CLIENT.CITY#
----------------------------------------------------------------------------
--------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a
message with 'unsubscribe' in the body to [EMAIL PROTECTED]
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
------------------------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists or send a message
with 'unsubscribe' in the body to [EMAIL PROTECTED]
