persistent shopping basket and price changes
In the book, the persistent shopping cart is stored as a serializable class in the asp.net profile system. The book claims that this saves the user the time and trouble of writing their own tables and stored procedures for accessing the shopping cart.
I have never implemented a persistent shopping cart like this. What would you do if the product information has changed since the user last visited the website. I guess when you first load the stored shopping basket you could check the shopping basket against the database to see if the products still exist and if their prices are still the same. However, doesnt the very fact you have to check the shopping basket against the database negate any benefits of storing the basket in the asp.net profile rather than in its own database tables?
thanks very much