Thanks Peter! Perhaps I coudl pick your brain a little more. :-) I am new to the whole shopping cart concept, thats why I decided to jump right in an build a basic one. I am fine setting up the DB for products and categories and what not, but one question I have been struggling with is how to store cart info? Is it best to assign a new CartID to every customer? I am having the user register before they can shop, so I could technically give them a CartID to use that never changes... then once they place an order, move the info into an orders table.. does this sound ok? I am open for any suggestions.. I hope these questions are not to annoying to you and the list.. :-)
Thanks, Mike ----- Original Message ----- From: "Peter Tilbrook" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Saturday, November 03, 2001 10:26 PM Subject: Re: Client Management > When using client variables CF automatically assigns a unique ID and Token > to the users browser. > > If the user connects with Internet Explorer CF will assign an ID and Token > like this (eg, in the URL): > > www.mysite.com/index.cfm?CFID=1457860&CFTOKEN=89645570 > > The same user connecting from the same machine with, say, Opera or Netscape > might have a different CFID/CFTOKEN value, eg: > > www.mysite.com/index.cfm?CFID=2943532&CFTOKEN=82324419 > > Client variables can identify "clients" by the browser - each unique > connection by a browser being assigned a unique CFID and CFTOKEN. The same > user connecting to your site from WORK would have a different ID/TOKEN > because they are using a different "client" (the browser). > > You have obviously turned on the feature to store client variables in the > database. This is good - better than the default of the registry. Client > variables can exist across sessions. If CF can match a client variable with > a client it can then use it - otherwise a new ID/TOKEN is assigned. > > Session variables are stored in the servers memory and are deleted when the > client is closed (the session ends). This is good for a shopping cart when > you do not want the cart stored when the user closes the browser. Other > wise use client variables. Remember to pass the variable URLToken in your > forms and links so CF can keep track of the current client. eg: > > Include in all of your form submissions: > > <input type="hidden" name="CFID" value="#CFID#"> > <input type="hidden" name="CFTOKEN" value="#CFTOKEN#"> > > Append to your URLS: > > <a href="mylink.cfm&#URLToken#"> > > And for CFLOCATION: > > <cflocation url="index.cfm" addtoken="Yes"> > > Notice the "addtoken"? > > Client variables are great when you can not be certain a users browser will > accept cookies. > > > > At 21:48 3/11/01 -0500, you wrote: > >Hi again everyone. > > > >I was wondering if someone could explain client management to me. > >I am developing a shopping cart as practice and have been reading up on > >Client management, Session Management, and how they relate... Does CF > >automatically check to see if a user has been to a certain application > >if client management is set to yes? I noticed there are 2 tables in my > >Database now that are from CF... I am just confused about the whole > >client management concept. > > > >Any explanation would be appreciated. > > > >Thanks, > >Mike Tangorre > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm 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
