I'm for storing them in a table. I suppose that if you wanted to allow "guest" shopping, you could assign a temporary user id (some UUID) and store it on their machine as a cookie, and then use that as a key in the "cart" table. That's just a thought off the top of my head, so there could be some issues that I've not thought about, but it seems like a solid idea.
Chris On 9/17/07, ColdFusion <[EMAIL PROTECTED]> wrote: > > Personally, I have them become a user before check out and then have the > items in a shopping cart table based on their user id. > That way it saves their cart for later purchase if needed. Else they can > remove the items. > > > > -----Original Message----- > From: Les Mizzell [mailto:[EMAIL PROTECTED] > Sent: Monday, September 17, 2007 10:41 AM > To: CF-Talk > Subject: Shopping Cart Theory > > I'm building a small shopping cart for a client - seems quicker to go from > scratch than try to wrestle something already built back into our specific > needs. Although I've done a couple of these, I was just wondering... > > What would the rest of you consider the optimal way to store items before > checking out? > > Session var with an array? > A temporary "holding database" for the items with just a UUID Session Var > to > keep up with the owner? > > I'm leaning towards the array in a session var - but this is on a shared > server and I've seen sessions time out unexpectedly before, which wouldn't > be good ("where'd all my stuff go???"). > > Anybody else? > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion 8 - Build next generation apps today, with easy PDF and Ajax features - download now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:288577 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
