I just store my quantity/description/price into structures named after the
ID (SKU in my case)

Cart[ID/SKU].Price
Cart[ID/SKU].ProductName
Cart[ID/SKU].Quanitity

This way all the info for "each" product is alltogether rather than in three
"lists".  Just a thought.

No listFind() anywhere in the code now.

> Hi everyone.
>
> I have just created a simple shopping cart and wanted to get some thoughts
on my approach to it.
>
> I create a structure of lists which is stored in the session scope.
>
> 1. cart.quantities
> 2. cart.prices
> 3. cart.products
>
> Basically every time I  (add/remove/changeqty) a product, I go through and
make changes to the three lists:
>
> Example:
>
> products list (holds product IDs)   1001, 1002, 1003, 1004
> price list (hold price for sinlge product) 5.99, 6.45, 2.50, 8.99
> quantity (holds quantity of product added) 2, 4, 1, 1
>
> So basically everytime I perform an operation, I use ListFind to get the
position in the list of the product whose ID is passed into the page. Using
that location of the product in the list, I just perform simple insertions,
deletions, and updates using the location.
>
> Does anyone see any downsides to this method?
> I build another cart using arrays, and the execution times for the
templates were considerably longer.
>
> Hit me back with some pros and cons or comments.
>
> Thanks,
> Mike
>
>
>
> 
______________________________________________________________________
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

Reply via email to