The above post was getting interesting a while back, several opinions where given, but none were substantial.
One interesting theory was the following: <quote>Because the session is being tied to the "Client" itself - i.e. the actual browser. If you try the same thing but with a different browser on the same machine it should work correctly.</quote> I tried it myself and did not get this to work, did anybody else? Also, I understand some of the differences between client and session scope. - Session scope is stored in Memory - Session scope can store complex objects - Client scope can be stored in Database, Cookie or Registry - Client scope should store long term variables Are there any properties I have missed that differentiate between them? Can anyone elaborate on the following "particular client and application and that must be saved between user sessions" Taken from the CF Docs Client Variables that are associated with one client. Client variables let you maintain state as a user moves from page to page in an application and are available across browser sessions. Use client variables for data that is associated with a particular client and application and that must be saved between user sessions. Use client variables for long-term information such as user display or content preferences. Session Variables that are associated with one client and persist only as long as the client maintains a session. Taco Fleur Blog http://www.tacofleur.com/index/blog/ Methodology http://www.tacofleur.com/index/methodology/ 0421 851 786 Tell me and I will forget Show me and I will remember Teach me and I will learn --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
