I personally favour client variables. But bear in mind that you must be using a proper DB server, NOT access for this to work. SQL, MYSQl Etc.
Additionally, in CF admin the client variables must be purged in a reasonable time if SQL disk space is in short supply or you get a billion hits a day. Use a structure for storing the basket contents by all means, however instead of session.basketContents, convert the structure to a WDDX object and store it as client.basketContents - That way you're not using precious RAM but cheap disk space. Martin Parry Macromedia Certified Developer http://www.BeetrootStreet.co.uk -----Original Message----- From: mayo [mailto:[EMAIL PROTECTED] Sent: 29 December 2004 02:13 To: CF-Talk Subject: shopping cart, session variables - best practices I'm setting up a shopping cart for a jewelry store. I'm curious, what is performance limit for storing data in session variables? The following are lists: Item No (itemID used in check out) Item Qty (in case someone wants more than one) Item Price Item Description (most descriptions about 50 characters. ex: "Ruby and gold drop-earrings") Most customers will not go above 3 or 4 items so I'm not concerned for this project. Just curious in general. At what point would storing data impact performance? Also, is updating session variables all that much quicker than updating a database. For example a customer wants two pairs of a particular earring instead of one. -- gil ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - New Atlanta http://www.newatlanta.com Message: http://www.houseoffusion.com/lists.cfm/link=i:4:188920 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
